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 just use my own custom built docker images and have a few aliases set up for different "instances", e.g. one for banking, one for tis eshop, one for that eshop, etc. Each with its own firefox data dir and own downloads subfolder. Plus an alias to launch a temporary clean instance that gets discarded after it exits.
That sound pretty cool - do these separate containers exit through the same network ? Or do you have like separate vpns?
All through the same network, I'm afraid. I haven't felt the need to separate it like that, although it should be doable using docker networks, or maybe on even lower level, via Linux network namespaces.