Fix Dokploy database and CORS config
This commit is contained in:
@@ -133,7 +133,7 @@ client address.
|
||||
|
||||
## Dokploy
|
||||
|
||||
Use `docker-compose.dev.yml` as the Dokploy compose path for a self-contained
|
||||
Use `docker-compose.prod.yml` as the Dokploy compose path for a self-contained
|
||||
backend deployment with MySQL and a local SMTP catcher. Configure the public
|
||||
domain in Dokploy against service `backend` and container port `5555`.
|
||||
|
||||
@@ -142,8 +142,10 @@ with Dokploy environment variables. The SMTP catcher service keeps the internal
|
||||
name `mailhog` for compatibility, but uses the multi-architecture Mailpit image
|
||||
to avoid `exec format error` failures on ARM servers.
|
||||
|
||||
Set `MYSQL_PASSWORD`, `MYSQL_ROOT_PASSWORD` and any other environment-specific
|
||||
values in Dokploy environment variables.
|
||||
Set `DB_NAME`, `DB_USER`, `DB_PASSWORD`, `MYSQL_ROOT_PASSWORD` and
|
||||
`CORS_ALLOWED_ORIGIN` in Dokploy environment variables. Use the exact browser
|
||||
origin without quotes or a trailing slash, for example
|
||||
`https://visione.studentindipendenti.it`.
|
||||
|
||||
## Current Endpoints
|
||||
|
||||
|
||||
Reference in New Issue
Block a user