arika
5c1e002233
* fix: use NODE_ENV when starting from docker image When starting from `pnpm run start`, NODE_ENV is fixed to production, causing problems like #186. So, I added `start_docker`, a process dedicated to docker, and started from it. The process is exactly the same as `start` except that NODE_ENV is not overwritten. * fix: align execution name with others * Change: command name to match review
18 lines
474 B
Bash
Executable File
18 lines
474 B
Bash
Executable File
#!/bin/sh
|
|
set -x
|
|
|
|
if [ -n "$DATABASE_HOST" ]; then
|
|
scripts/wait-for-it.sh ${DATABASE_HOST} -- echo "database is up"
|
|
fi
|
|
|
|
# Run migrations
|
|
pnpm --filter @trigger.dev/database db:migrate:deploy
|
|
|
|
# Copy over required prisma files and invoke bundled seed file
|
|
cp packages/database/prisma/schema.prisma apps/webapp/prisma/
|
|
cp node_modules/@prisma/engines/*.node apps/webapp/prisma/
|
|
pnpm --filter webapp db:seed
|
|
|
|
cd /triggerdotdev/apps/webapp
|
|
exec dumb-init pnpm run start:local
|