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!
I fully admit I’m not the most talented linux person, but you say that you created an smb share on Unraid, but you mounted it as if it were an NFS share. Is that just a typo, or could that be the root of your problem? I could imagine Synology Drive not letting you interact with files in the mounted folder if the permissions and ownership weren’t set up right.
Regarding the SMB-share, let my try to clarify.
Let's say you have 3 machines. 192.168.1.10/20/30. On machine 10 a folder synology
which has a network folder mounted onto it from machine 20 mount -t nfs 192.168.1.20:/some/folder synology
.
Now you want to access that folder on machine 30. Here you can't use mount -t nfs
but MUST use mount -t cifs
instead, because you cannot forward a mounted share. However, this is not the problem, it's just a description of my current setup.
Regarding the ownership. Your point is very valid, but I ruled that out already. I did a so-called bind-mount within Synology with the exact user permissions as in the users home folder, but this didn't work.
FYI: a bind-mount is where you have two folders /foo
(with many sub-folders and files) and /bar (empty)
. If you do mount --bind /foo /bar
, then the system thinks that bar is a real folder with the subfolders and files (from foo, including their permissions).
Thank you for going to the extra trouble to explain this! This is why I love communities like this.