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
Thanks for the feedback!
A docker could make the setup run, and if I rework where I store the data (now it's in the same folder as the listener so it needs a special tweak in the docker files) but the problem is the 10f executable that you use to share files with, it's a command line app so it would be weird to put that in a docker IMO.
Also, using docker images isn't really simple?
You are right though, simpler is better.
What do you think about a setup script instead? Like
forward a port to your PC
run the setup script with your public IP:PORT (or just the port and let the script auto-detect the IP)
start the listener
Or should I still work on that? I can make a gui that helps setting everything up and run I guess.