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] 17 points 1 year ago (3 children)

Or just use the Watchtower container to auto-update them 😉

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

I don’t like the auto update function. I also use a script similar to the one op uses (with a .ignore file added). I like to be in control when (or if) updates happen. I use watchtower as a notification service.

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

I scream test myself… kidding aside, I try to pin to major versions where possible — Postgres:16-alpine for example will generally not break between updates and things should just chip along. It’s when indie devs not tagging anything other than latest or adhere to semantic versioning best practices where I keep watchtower off and update once in a blue moon manually as a result.

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

Exactly, when it updates, I want to initiate it to make sure everything goes as it should.

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

Nothing off mine is that important that I couldn't create/rollback the container if it does happen to screw up.

[–] d13 1 points 1 year ago

I prefer manually updating so that I can sanity-test for breaking changes.

I have a script like the one above but I don't loop through the services; I just run it for each service and then test it. I also only have it delete versions of a certain age.

[–] Zikeji 1 points 1 year ago

I use Diun to notify me when an image is updated. I also use strict versions in my compose file, that way if I have to restore to another system I don't soft brick a container due to a breaking version change.