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:
- 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
How has been your experience with code-server so far? I am interested in self-hosting it
I'm also curious about this -- there's a usecase I have that I think fits, but I'm not sure if I'm either barking up the wrong tree, or overthinking it.
What I'd like to do is open up VSCode on any of my computers, make changes to files, save them, and see those reflected when I open VSCode on another PC.
I suspect VSCode container is meant for people who are actually developing and running their code and need an environment catered to that.
Am I better off doing something like saving my files to folder on a network share and then just opening that folder in VSCode on each PC instead? Is that even possible?
Using a network share for that specific usecase may be a great option. I think VSCode server may be more practical for collaborative work or for PCs with limited resources.