Basic Cleanup in docker-compose files for convenience and Readme fixing #9
No reviewers
Labels
No labels
Documentation
Infrastructure
Redaktions-App
User-App
backend
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Effort
High
Effort
Low
Effort
Medium
Prio
High
Prio
Low
Prio
Medium
Type
Bug
Type
Feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: NB-Public/kandimat#9
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/9/head"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I think we should stick with latest
I think this is the point where it starts being obivous that this file does not render a production ready configuration. Let's delete docker-compose.prod.yml completely for now. It only adds the illusion of a prod-ready setup, which it is not (for example postgraphile should start with completely different parameters in production and there should be a repo independent secret management in place). Let's worry about a prod setup the moment we actually want to go to production. As for the volume thing: Let's add it to the dev yaml.
If you want to use a clean database you can still comment it out or delete the volumes by hand.
Thanks for the very necessary adaptions.