100
submitted 6 months ago* (last edited 6 months ago) by passepartout@feddit.de to c/selfhosted@lemmy.world

Upgrade went mostly without a problem (had set more than one Hostname for a service before, seems to not work anymore lol), and i have a pretty large configuration that has grown over the past two years.

What i noticed is that it is quite a bit faster. Also the dashboard shows a little more information than before and the logs have colours now.

you are viewing a single comment's thread
view the rest of the comments
[-] Appoxo@lemmy.dbzer0.com 8 points 6 months ago

Found it out the hard way because I have automatic updates with watchtower... xD

[-] MangoPenguin@lemmy.blahaj.zone 7 points 6 months ago* (last edited 6 months ago)

Definitely worth using specific versions on your docker images if you're doing automatic updates.

traefik:mimolette for example should keep you on 2.x versions while still getting patches and bug fixes.

[-] Appoxo@lemmy.dbzer0.com 1 points 6 months ago

Yeah...I should be doing it but I am honestly too lazy to change my compose.
The only place I actually did it is my mongodb container bexause I know absolutely nothing about it.
At lwast I can rescue my traefik config :p

[-] MangoPenguin@lemmy.blahaj.zone 2 points 6 months ago

I mean same, I say it's worth using but I don't do it either haha.

Everything is backed up every night, so if something breaks to the point of data loss I just fix it after.

[-] thegreekgeek@midwest.social 2 points 6 months ago

Oof, that's what killed my V1 setup lol

[-] passepartout@feddit.de 1 points 6 months ago

I hope it went well :) i was completely ready to go back changing the image tag to v2 but didn't need to.

[-] Appoxo@lemmy.dbzer0.com 2 points 6 months ago

Juat an error due to the swarmRefresh setting in the traefik.yml.
Because I am not running in swarm mode it threw an error.
Oh well. Life and learn ¯\_(ツ)_/¯

this post was submitted on 01 May 2024
100 points (98.1% liked)

Selfhosted

39677 readers
403 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS