this post was submitted on 12 Feb 2026
109 points (99.1% liked)

Selfhosted

61030 readers
635 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

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
109
Vaultwarden security update Feb 10 2026 (github.com)
submitted 5 months ago by megaman@discuss.tchncs.de to c/selfhosted@lemmy.world
14 comments fedilink hide all child comments
 

GHSA-h265-g7rm-h337 (Publication in process, waiting for CVE assignment) This vulnerability would allow an authenticated attacker that is part of an organization to access items from collections to which the attacker does not belong

you are viewing a single comment's thread
view the rest of the comments
[–] tofu@lemmy.nocturnal.garden 22 points 5 months ago (2 children)

Already updated yesterday 🤓 All hail the mighty renovate

[–] Natanox@discuss.tchncs.de 2 points 5 months ago (2 children)

Renovate?

[–] tofu@lemmy.nocturnal.garden 7 points 5 months ago

I have all my compose stacks in git. They're deployed from their git repos with Komodo.

Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there's a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It's a great semi automatic way to handle updates without giving up control.

There's a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo

[–] qaz@lemmy.world 1 points 5 months ago (1 children)

It's a bot to create PR's with dependency updates

[–] Natanox@discuss.tchncs.de 2 points 5 months ago (1 children)

Might be a stupid question, but how are PR's connected to your server deployment?

[–] tofu@lemmy.nocturnal.garden 2 points 5 months ago

Copying my other comment. It opens PRs to change the tag from the docker image.

I have all my compose stacks in git. They’re deployed from their git repos with Komodo.

Renovate is a bot that checks git repos for dependencies (mostly container images in this case) and checks if there’s a newer version available. If yes, it creates a merge request to update the version. I review the requests and merge, then the updated compose stack gets deployed with Komodo. It’s a great semi automatic way to handle updates without giving up control.

There’s a nice how to here: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo

[–] motruck@lemmy.zip 1 points 5 months ago (1 children)

Renovate? Hrmmmm