Standardise service names? #19
Closed
opened 2020-09-25 23:26:31 +00:00 by 3wordchant
·
11 comments
Labels
Clear labels
abra
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
design
documentation
duplicate
enhancement
fedi
fedi-infra
finance
funding
good first issue
help wanted
installer
legal
performance
proposal
question
security
test
wontfix
Everything to do with abra
Ping/pong on comms
Something is not working
Go build related issues
Getting the robots into the mix
Opening this thing up
Contributors stuff
Our main website
Design thinking required
Let's write things together
This issue or pull request already exists
New feature
Democratic decision making
Money things
Anything related to grant funding
Easy start with development
Need some help
Installation related issues
Performance related
Large change which requires feedback & decisin making
More information is needed
Securing our shit
Unit or integration test suite
This won't be fixed
No labels
question
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
BornDeleuze
Brooke
carla
cas (Cassowary)
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
iexos
jade (Jade Ambrose)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
moosemower
moritz
notplants
oxaliq (sorrel)
p4u1
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
renovate-bot (Comrade Renovate Bot)
ripclap
simon
sixsmith (Sixsmith)
stevensting
trav (Trav Fryer)
val (val (he/him))
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#19
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
abramake a sensible guess when you run e.g.abra runwith 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
appdoesn'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 rmfirst...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!