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 use syncthing like you on a Linux laptop with two users. You need to run two instances of syncthing on two different ports then there is no problem.
Let me get this straight. Ur saying that on the laptop I have two instances, one for me and one for my wife and they both sync to nas instance. I have syncthing installed via apt on my Debian laptop. How do u get two instances going?
Yes exactly, but not only to the NAS but also between each other.
First you need to change the UI port on the second user, to do that you have to change it in the config XML file for that user.
Once done you can start both instances at the same time. How do you start it now? I'm starting it with systems, and there is the way to start it for each user seperatelly on boot with:
systemctl enable syncthing@myuser.service
systemctl start syncthing@myuser.service
Dis is da wey
Anti Commercial-AI license