So, i have a NextCloud instance running, with the data directory binded to a folder on my storage. Now, when ik want to list or edit the contents of this folder directly from Nautilus or the terminal, I get a permission denied message. Obviously i do not have sufficent rights. How do i give myself permissions to at least view the contents of the folder? Maybe this is basis linux stuff, I have just not touched this before, and I don’t want to modify this folder or break my NextCloud ;)
Generally, in my experience, modifying the backing storage for a nextcloud instance is more of a PITA than its worth. I would just mount the webDAV in your file manager. This way the nextcloud db stays in sync with the backing storage.
If you are going to be making direct modifications to the backing storage, check this form post on modifying the nextcloud config to have it look for changes on the filesystem.
As for the permission side of things, run ls -lh in the folder that you want to make changes and see what the user:group is for ownership of the existing files and make sure your new files match. Chmod and chown will be your friends here and chmod has a --reference option that let’s you mirror permissions from an existing file, a real time saver.
I hadn’t thought of the database issue, thanks! I am afraid though that changing the ownership of the folder might break things though? Love the --reference option by the way
I would cd into the user folder that you want to add / remove files from and see what the ownership is to begin with and simply replicate ownership to match what’s already there.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
Generally, in my experience, modifying the backing storage for a nextcloud instance is more of a PITA than its worth. I would just mount the webDAV in your file manager. This way the nextcloud db stays in sync with the backing storage.
If you are going to be making direct modifications to the backing storage, check this form post on modifying the nextcloud config to have it look for changes on the filesystem.
As for the permission side of things, run ls -lh in the folder that you want to make changes and see what the user:group is for ownership of the existing files and make sure your new files match. Chmod and chown will be your friends here and chmod has a --reference option that let’s you mirror permissions from an existing file, a real time saver.
Hopefully this helps!
I hadn’t thought of the database issue, thanks! I am afraid though that changing the ownership of the folder might break things though? Love the --reference option by the way
I would cd into the user folder that you want to add / remove files from and see what the ownership is to begin with and simply replicate ownership to match what’s already there.
I went with the suggested mount as webdav, and this works out fine for me, thanks