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: 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:
- 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 got tired of the NPM and went to traefik for 2 reasons.
NPM kept locking me out of my account (admin), like 4 times during the time I was using it. That meant that it was not reliable enough for daily use.
From what I heard is that the NPM project only has 1 developer and so they can't really respond and fix security flaws in a proper timeframe.
I'm using traefik now for internal traffic while VPN in if I need internal services while out and about.
Jim's Garage has a great YouTube video on setting it up.
How did you set up a VPN to securely connect to your services over the internet? I have looked for guides to do this and haven't had much luck. I would really like to implement this in my setup.
I can once again refer to Jim's Garages video about setting up wireguard on Docker. Very easy.
Wg-easy, with a nice interface.
Thank you, I wasn't sure if that video was re: Traefik or VPN. I appreciate the suggestion.
It's mostly just nginx with a webui. You can even see the nginx config files if you bash into the container. It has the same bugs as upstream nginx. Do not expose the management port to the internet.
Plus compared to normal nginx, it's harder to misconfigure it. Most of my services are just the default config, so I can't mess it up accidentally.
About lockouts: Once also happened me, but that was just a messed up update, next update fixed itself. If you lock yourself out you can usually edit the db directly, it defaults to sqlite, but I used it with mariadb.