Skip to content
Discussion options

You must be logged in to vote

@rmsferreira you were right, and thank you for the report — sorry it sat this long.

docker-compose.prod.yml was 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.yml defaults ENVIRONMENT to development; development is in AUTH_BYPASS_ENVIRONMENTS; and services/api/app/api/v1/dev_auth.py resolves a request carrying no bearer token to a demo user whose role is admin. Measured both ways:

ENVIRONMENT U…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by beenuar
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants