Selfhosted

60409 readers

501 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

124

Self hosting Sunday! What's up, selfhosters? (lemmy.nocturnal.garden)

submitted 7 months ago by tofu@lemmy.nocturnal.garden to c/selfhosted@lemmy.world

99 comments fedilink hide all child comments

How's your stuff doing? Unplanned interruptions or achieving uptime records?

I'm currently sailing rather smooth. Most of my stuff is migrated to Komodo, there will stay some exceptions and I only have to migrate Lemmy itself I think. Of course that's when I found a potential replacement but I'll let it sit for a while before touching it again. Enjoying the occasional Merge Request notification from the Renovate Bot and knowing my stuff is mostly up to date.

I'm thinking about setting up some kind of Wiki for my other niche hobby (Netrunner LCG) lore as there's a fandom one that most people avoid touching and updating but since I likely won't have time to start writing some articles on my own as a kickoff I'm hesitant. Also not sure which wiki I'd choose as well.

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

[–] irmadlad@lemmy.world 4 points 7 months ago (2 children)

Just got watchtower running and going to see how it does before trying out some other automations.

If you find that watchtower (original) screws up the updates frequently there is a watchtower fork that runs so much smoother. I don't have any issues with it at all. The original watchtower app hasn't had an update in 2 years, so it might be something to keep in mind.

[–] silmarine@discuss.tchncs.de 4 points 7 months ago (1 children)

I'm actually using this one which seems to be more actively maintained than the one you linked.

[–] irmadlad@lemmy.world 3 points 7 months ago

Bookmarked! Thanks for that. Learning all kinds of stuff today.

[–] frongt@lemmy.zip 2 points 7 months ago (1 children)

In fact you must use the fork. The old one no longer works with recent Docker, due to API versioning. I found that out last night when I brought up my compose stack and traefik wouldn't start, because it too needed an update.

[–] irmadlad@lemmy.world 1 points 7 months ago

no longer works with recent Docker, due to API versioning

I had that issue with Portainer recently. I had to drop back to the previous docker version, and held it until Portainer works through the snag. I didn't think about original watchtower being affected. I just got tired of having to fix broken updates, and went looking for something better. When original watchtower worked tho, it worked well.