Repository navigation
Deployment Docker production #629
|
I see in the documentation the capability for deploy on Docker in Production using docker-compose.prod.yaml., however, I don’t see this file. |
Replies: 2 comments
|
The current one is strictly demo. Devs reference the docker-compose.prod.yaml but do not provide it. @beenuar will there be one with functioning auth? |
|
@rmsferreira you were right, and thank you for the report — sorry it sat this long.
@iliyandobrev-dreamix your question was the more important one, and the answer was no.
There was a documented one-line escape — What now exists
make env # generates the six service secrets
docker compose -f docker-compose.prod.yml up -dThe deployment page now also states plainly that the development stack has the bypass active, which it should have said all along. |
@rmsferreira you were right, and thank you for the report — sorry it sat this long.
docker-compose.prod.ymlwas referenced in two places on the deployment page (the flavors table, and a runnable command under "## Production") and the file never existed. The documented production command failed on a missing file, which is worse than an undocumented path.@iliyandobrev-dreamix your question was the more important one, and the answer was no.
docker-compose.ymldefaultsENVIRONMENTtodevelopment;developmentis inAUTH_BYPASS_ENVIRONMENTS; andservices/api/app/api/v1/dev_auth.pyresolves a request carrying no bearer token to a demo user whose role isadmin. Measured both ways:ENVIRONMENT