Selfhosted
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.
-
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. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
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:
- 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!
view the rest of the comments
I do this. Plus VPN to have access to passwords when away from home network
What’s the issue of exposing this one to the internet? Even if the database gets leaked somehow, your passwords are still protected by a hopefully strong master password + strong encryption
I guess it's due to unnecessary risk and lazyness of not wanting to get a domain for TLS. Mostly the unnecessary risk, like why expose it when I don't have to.
Because it lets you sync your passwords anytime, without having to connect to the VPN first, which saves time. And the risk of data leak is not really there since the passwords are encrypted by a strong master password anyways. With Vaultwarden, you can host your database even publicly and share it on Lemmy and nothing would happen, provided you use a strong master password, which you definitely should.