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
Currently dealing with this nonsense,
and this accompanying nonsense:
Why is your Collabora server on local host? Local host will always point to the device you are trying to access from. You need a publicly accessible URL
"Local host" in this instance refers to my desktop computer where all my super sweet Linux distros are saved. Nextcloud Office, while being an "app" appears to not have any function without the collabora; i.e. there will be no document viewer without the collabora "server" running next to NextCloud.
Or maybe it's none of that. Coming from a Windows background, running docker is completely foreign.
Collabora need to be accessible at the URL you provide. As a example one might have nextcloud at nc.example.com and Collabora as cb.example.com. you would need to enter cb.example.com as the URL.
The easier way it to use the Nextcloud all in one image or the build in Collabora. Its not going to be as robust or fast but its much simpler.