fix: let Coolify provide runtime env
This commit is contained in:
@@ -13,7 +13,7 @@ npm run start # Start production server
|
||||
npm run lint # ESLint (eslint-config-next/core-web-vitals + typescript)
|
||||
```
|
||||
|
||||
Docker deployment: port 8019, `docker-compose up` with `.env.production`, external network `sinobridge`.
|
||||
Docker deployment: port 8019, `docker-compose up` with env supplied by the deployment platform or shell, external network `sinobridge`.
|
||||
|
||||
## Architecture
|
||||
|
||||
|
||||
@@ -74,7 +74,7 @@ The included Dockerfile builds a standalone Next.js output and starts `server.js
|
||||
docker compose up -d --build
|
||||
```
|
||||
|
||||
`docker-compose.yml` expects `.env.production` and an external Docker network named `sinobridge`.
|
||||
Set the required environment variables through your deployment platform or shell before starting Compose. The included `docker-compose.yml` expects an external Docker network named `sinobridge`.
|
||||
|
||||
## Operational Notes
|
||||
|
||||
|
||||
@@ -5,8 +5,6 @@ services:
|
||||
restart: unless-stopped
|
||||
ports:
|
||||
- "8019:8019"
|
||||
env_file:
|
||||
- .env.production
|
||||
networks:
|
||||
- sinobridge
|
||||
|
||||
|
||||
Reference in New Issue
Block a user