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
For a quick test you could set it to 777, if that fixes it, check which user new files are being assigned to, adjust permissions back down accordingly.
I tried it, I still can upload files to the server when I go to Upload Files section but it redirect to the 404 I think due to the Short Urls. The images still upload to the server fine but its a hassle because it always looks like it fails. I don't know how to fix the Short Urls issue though
and if i try to upload an image from the Upload Image section when editing the wiki it gives me the old HTTP 500 error.
the problem is that it thinks the files are located at /view/File:filename.png
but they're really located at index.php?title=File:filename.png