mirror/FileRise
1
0
Fork 0
mirror of https://github.com/error311/FileRise.git synced 2025-12-21 10:59:38 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify manual data dir creation and fix update script link

Browse Source
This commit is contained in:
Ryan
2025-12-10 03:12:55 -05:00
committed by GitHub
parent 0e9edd92d7
commit c65f11a724
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -224,7 +224,13 @@ FileRise ships as a standard PHP app with this layout:
- `config/`
- `public/` ← web server **DocumentRoot**
- `src/`
- `uploads/`, `users/`, `metadata/` (created on first run / install)
- `uploads/`, `users/`, `metadata/` (data directories; you can create them up front as shown below — FileRise will attempt to create them on first run if they’re missing and permissions allow)
```bash
mkdir -p uploads users metadata
chown -R www-data:www-data uploads users metadata # adjust for your web user
chmod -R 775 uploads users metadata
```
You can install from a **release ZIP** (recommended) or from **git**.
@@ -322,7 +328,7 @@ For detailed examples and reverse proxy snippets, see the Wiki:
If you deployed FileRise directly in `/var/www`, you can use this helper script
to update to a new release without touching your data.
Save this as `scripts/update-filerise.sh` [update-filerise.sh](error311/FileRise/scripts/update-filerise.sh) (make it executable with `chmod +x scripts/update-filerise.sh`):
Save this as `scripts/update-filerise.sh` [update-filerise.sh](scripts/update-filerise.sh) (make it executable with `chmod +x scripts/update-filerise.sh`):
---