Selfhosted

39435 readers

3 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

I'm using compose wrong and I know it. (lemmy.one)

submitted 1 year ago by [email protected] to c/[email protected]

40 comments fedilink hide all child comments

For the last two years, I've been treating compose files as individual runners for individual programs.

Then I brainstormed the concept of having one singular docker-compose file that writes out every single running container on my system... (that can use compose), each install starts at the same root directory and volumes branch out from there.

Then I find out, this is how most people use compose. One compose file, with volumes and directories branching out from wherever ./ is called.

THEN I FIND OUT... that most people that discover this move their installations to podman because compose works on different versions per app and calling those versions breaks the concept of having one singular docker-compose.yml file and podman doesn't need a version for compose files.

Is there some meta for the best way to handle these apps collectively?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 30 points 1 year ago (2 children)

I think compose is best used somewhere in between.

I like to have separate compose files for all my service "stacks". Sometimes that's a frontend, backend, and database. Other times it's just a single container.

It's all about how you want to organize things.

[–] [email protected] 13 points 1 year ago

I do this, 1 compose file per application. That has all the things that application need, volumes, networks, secrets.

In single docker host land, each application even has its own folder with the compose file and any other artifacts in it.

[–] [email protected] 3 points 1 year ago

Yeah this post had me a little worried I’m doing something wrong haha. But I do it just like that. Compose file per stack.