Standardise service names? #19
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#19
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?
There seem to be two competing standards for service naming; let's call them "specific":
and "generic":
I had been leaning towards "specific" for clarity in things like container names, but I think it's getting near Smurf naming territory (
wordpress_wordpress..
), and Docker-fluent upstreams like Nextcloud seem to be converging on "generic".Another advantage of "generic" is it would help
abra
make a sensible guess when you run e.g.abra run
with no arguments, where currently we'd need to parsecompose.yml
(and rely on consistent ordering..) or save the default service in per-stack configuration.Good point! I'm easy on this but whichever way we go I think we should probably start some sort of style guide for this. "Generic" is the one we'd lean towards then?
Yeah currently "generic" is seeming better, that's what I used for
compose-stacks/postfix-relay
. Compose file style guide definitely seems like a good move.Leaving this open to track converting existing repos to "generic" format.
Yeah nice! We're now in a funny situation where its like "oh sick, I got this new app converted into a config and it works!" and "oh no, now we have more configs to change and maintain". It's great and not great :)
I am fine taking responsibility for the forest of apps I've grown for the foreseeable future 🙃
Still left:
Not sure about Renovate, given it's not expected to be running anyway?
I guess
app
doesn't quite cut it but maybe we can just use it anyway :)Kimai, Keycloak and Portainer done 👌
Just ran through the last ones, watch out on your re-deploys! Better
stack rm
first...Hmmm, FYI, I just went through a configuration fiasco because the traefik-forward-auth container expects a non-generic naming of the service definition. So, sometimes it is not possible. I think this is the only exception but just good to know.
Ah nice spot, thank you!