Skip to content

Commit c65f11a

Browse files
authored
docs: clarify manual data dir creation and fix update script link
1 parent 0e9edd9 commit c65f11a

1 file changed

Lines changed: 8 additions & 2 deletions

File tree

README.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -224,7 +224,13 @@ FileRise ships as a standard PHP app with this layout:
224224
- `config/`
225225
- `public/` ← web server **DocumentRoot**
226226
- `src/`
227-
- `uploads/`, `users/`, `metadata/` (created on first run / install)
227+
- `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)
228+
229+
```bash
230+
mkdir -p uploads users metadata
231+
chown -R www-data:www-data uploads users metadata # adjust for your web user
232+
chmod -R 775 uploads users metadata
233+
```
228234

229235
You can install from a **release ZIP** (recommended) or from **git**.
230236

@@ -322,7 +328,7 @@ For detailed examples and reverse proxy snippets, see the Wiki:
322328
If you deployed FileRise directly in `/var/www`, you can use this helper script
323329
to update to a new release without touching your data.
324330

325-
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`):
331+
Save this as `scripts/update-filerise.sh` [update-filerise.sh](scripts/update-filerise.sh) (make it executable with `chmod +x scripts/update-filerise.sh`):
326332

327333
---
328334

0 commit comments

Comments
 (0)