jason/mrp
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

confirm actions

Browse Source
This commit is contained in:
jason
2026-03-15 18:59:37 -05:00
parent 59754c7657
commit df041254da
28 changed files with 999 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
UNRAID.md
View File

@@ -106,7 +106,7 @@ If you do not set them, the defaults from the app bootstrapping logic are used.
On first container start, the entrypoint will:
1. Ensure `/app/data/prisma` and `/app/data/uploads` exist
2. Run `npx prisma migrate deploy`
2. Run `/app/server/node_modules/.bin/prisma migrate deploy --schema /app/server/prisma/schema.prisma`
3. Start the Node.js server
The frontend is served by the same container as the API, so there is only one exposed web port.
@@ -130,7 +130,7 @@ When you publish a new image:
Because MRP Codex runs `prisma migrate deploy` during startup, committed migrations are applied automatically before the app launches.
This is especially important now that recent releases added CRM expansion, inventory transactions, sales and purchasing documents, shipping/logistics documents, the inventory `defaultPrice` field, purchasable-only purchase-order item selection, the new projects domain, and manufacturing work orders. Let the container complete startup migrations before testing new screens.
This is especially important now that recent releases added CRM expansion, inventory transactions, sales and purchasing documents, shipping/logistics documents, the inventory `defaultPrice` field, purchasable-only purchase-order item selection, the new projects domain, manufacturing work orders, audit tooling, and persisted auth sessions. Let the container complete startup migrations before testing new screens.
## Backup guidance