fix `db-up` / `db-nuke` command (#917)
`db-nuke` wasn't properly deleting the docker containerpull/918/head^2
parent
cfd70172f0
commit
c94231f777
|
@ -7,10 +7,10 @@
|
|||
"analyze:server": "BUNDLE_ANALYZE=server next build",
|
||||
"analyze:browser": "BUNDLE_ANALYZE=browser next build",
|
||||
"dev": "next dev",
|
||||
"db-up": "docker compose up -d",
|
||||
"db-up": "docker-compose up -d",
|
||||
"db-migrate": "yarn prisma migrate dev",
|
||||
"db-seed": "yarn ts-node scripts/seed.ts",
|
||||
"db-nuke": "docker compose down --volumes --remove-orphans",
|
||||
"db-nuke": "docker-compose down --volumes --remove-orphans",
|
||||
"dx": "cross-env BASE_URL=http://localhost:3000 JWT_SECRET=secret DATABASE_URL=postgresql://postgres:@localhost:5450/calendso run-s db-up db-migrate db-seed dev",
|
||||
"test": "jest",
|
||||
"test-playwright": "jest --maxWorkers=2 --config jest.playwright.config.js && nyc report --reporter=lcov",
|
||||
|
|
Loading…
Reference in New Issue