You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -224,7 +224,13 @@ FileRise ships as a standard PHP app with this layout:
224
224
-`config/`
225
225
-`public/` ← web server **DocumentRoot**
226
226
-`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
+
```
228
234
229
235
You can install from a **release ZIP** (recommended) or from **git**.
230
236
@@ -322,7 +328,7 @@ For detailed examples and reverse proxy snippets, see the Wiki:
322
328
If you deployed FileRise directly in `/var/www`, you can use this helper script
323
329
to update to a new release without touching your data.
324
330
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`):
0 commit comments