Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
services:filebrowser [2024/03/22 07:59] – created willy | services:filebrowser [Unknown date] (current) – removed - external edit (Unknown date) 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== Fileserver access via Browser ===== | ||
- | There are a few software out there, but i like [[https:// | ||
- | |||
- | // | ||
- | - bin: where the FileBrowser binary will be located | ||
- | - data/db: where the FileBrowser databases files will be stored | ||
- | - data/logs: where the various log files will be created | ||
- | |||
- | You need to set the //umask// for the user to **0002** so that any new files created by it will be writable by the users. | ||
- | |||
- | Then, as // | ||
- | <code bash> | ||
- | su - fileserver | ||
- | echo "umask 0002" >> ~/.bashrc | ||
- | source ~/.bashrc | ||
- | mkdir bin data data/logs data/db | ||
- | cd bin | ||
- | tar xvf ../ | ||
- | </ | ||
- | |||
- | Now, you will need to start a copy of FileBrowser for each share you want to have, and it must be owned by the user that want file permissions on that share. To achieve this, you will be using a special script called **fileserver.sh** which i will show you at the end, because it will contain also the WebDAV start stuff in it. |