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: _includes/parse-server/file-adapters.md
+35-7Lines changed: 35 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,31 @@
1
+
# Configuring File Upload
2
+
3
+
*Available on Parse Server >=5.0.0*
4
+
5
+
Parse Server restricts file upload to authenticated users only to improve Parse Server's default security. This behaviour can be modified by specifying `fileUpload` options to your Parse Server configuration.
6
+
7
+
Available options are:
8
+
9
+
-`enableForAnonymousUser`: Enable file upload for anonymous users
10
+
-`enableForAuthenticatedUser`: Enable file upload for authenticated users
11
+
-`enableForPublic`: Enable file upload for the public, i.e. everyone
encryptionKey:process.env.PARSE_SERVER_ENCRYPTION_KEY, //Add your file key here. Keep it secret
37
65
...
38
66
});
39
67
```
40
68
41
-
Be sure not to lose your key or change it after encrypting files.
69
+
Be sure not to lose your key or change it after encrypting files.
42
70
43
71
### Enabling encryption on a server that already has unencrypted files
44
72
When this is the case, it is recommended to start up a development parse-server (or a separate process from your main process) that has the same configuration as your production server. On the development server, initialize the file adapter as above with the new key and do the following after initialization in your `index.js`:
Be sure not to lose your key or change it after encrypting files.
389
+
Be sure not to lose your key or change it after encrypting files.
362
390
363
391
### Enabling encryption on a server that already has unencrypted files
364
392
When this is the case, it is recommended to start up a development parse-server (or a separate process from your main process) that has the same configuration as your production server. On the development server, initialize the file adapter as above with the new key and do the following after initialization in your `index.js`:
0 commit comments