Optional services in a stack? #11
Labels
No Label
automation
bug
community organising
democracy
design
documentation
duplicate
enhancement
finance
funding
help wanted
invalid
publishing
question
security
wontfix
No Milestone
No project
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#11
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
Seems like there'd be a few apps where people might not always want All The Services, All The Time, e.g. people:
Found an interesting approach:
Yeah that is quite nice. I was originally doing a
docker-compose.yml
/docker-compose.dev.yml
/docker-compose.prod.yml
thing but realised it is much easier to grok with a single file. This use case makes a lot of sense though. Maybe we could make acompose.d
or something where we put optional services and then document or makeabra
support that?Another approach is of course, a generator using cookiecutter / Jinja2 or something which asks you what you want when you generate the configuration. That speaks to a slightly more complicated and general solution which I don't really want to look into yet because it feels a bit YAGNI.
COMPOSE_FILE
doesn't work with Swarm, but I added (slightly lazy..) handling inabra
and it's working great e.g. for Mediawiki with SAML.