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
|`apps`| Array<Object>| no | - |`[{ ... }, { ... }]`| The apps that are configured for the dashboard. |
148
-
|`apps.appId`| String | yes | - |`"myAppId"`| The Application ID for your Parse Server instance. |
149
-
|`apps.masterKey`| String \| Function | yes | - |`"exampleMasterKey"`, `() => "exampleMasterKey"`| The master key for full access to Parse Server. It can be provided directly as a String or as a Function returning a String. |
150
-
|`apps.masterKeyTtl`| Number | no | - |`3600`| Time-to-live (TTL) for the master key in seconds. This defines how long the master key is cached before the `masterKey` function is re-triggered. |
151
-
|`apps.serverURL`| String | yes | - |`"http://localhost:1337/parse"`| The URL where your Parse Server is running. |
152
-
|`apps.appName`| String | no | - |`"MyApp"`| The display name of the app in the dashboard. |
|`infoPanel[*].title`| String | no | - |`User Details`| The panel title. |
155
-
|`infoPanel[*].classes`| Array<String>| no | - |`["_User"]`| The classes for which the info panel should be displayed. |
156
-
|`infoPanel[*].cloudCodeFunction`| String | no | - |`getUserDetails`| The Cloud Code Function which received the selected object in the data browser and returns the response to be displayed in the info panel. |
157
-
|`infoPanel[*].prefetchObjects`| Number | yes |`0`|`2`| Number of next rows to prefetch when browsing sequential rows. For example, `2` means the next 2 rows will be fetched in advance. |
158
-
|`infoPanel[*].prefetchStale`| Number | yes |`0`|`10`| Duration in seconds after which prefetched data is discarded as stale. |
159
-
|`apps.scripts`| Array<Object>| yes |`[]`|`[{ ... }, { ... }]`| The scripts that can be executed for that app. |
160
-
|`apps.scripts.title`| String | no | - |`'Delete User'`| The title that will be displayed in the data browser context menu and the script run confirmation dialog. |
161
-
|`apps.scripts.classes`| Array<String>| no | - |`['_User']`| The classes of Parse Objects for which the scripts can be executed. |
162
-
|`apps.scripts.cloudCodeFunction`| String | no | - |`'deleteUser'`| The name of the Parse Cloud Function to execute. |
163
-
|`apps.scripts.executionBatchSize`| Integer | yes |`1`|`10`| The batch size with which a script should be executed on all selected objects. For example, with 50 objects selected, a batch size of 10 means the script will run on 10 objects in parallel, running a total of 5 batches in serial. |
164
-
|`apps.scripts.showConfirmationDialog`| Bool | yes |`false`|`true`| Is `true` if a confirmation dialog should be displayed before the script is executed, `false` if the script should be executed immediately. |
165
-
|`apps.scripts.confirmationDialogStyle`| String | yes |`info`|`critical`| The style of the confirmation dialog. Valid values: `info` (blue style), `critical` (red style). |
166
-
| `apps.cloudConfigHistoryLimit` | Integer | yes | `100` | `100` | The number of historic values that should be saved in the Cloud Config change history. Valid values: `0`...`Number.MAX_SAFE_INTEGER`.
167
-
| `apps.config` | Object | yes | - | `{ ... }` | App settings option used to store dashboard configuration on the server.
168
-
|`apps.config.className`| String | yes |_|`DashboardConfig`| The table name used to save and migrate the dashboard configuration. |
169
-
145
+
This section provides a comprehensive reference for all Parse Dashboard configuration options that can be used in the configuration file, via CLI arguments, or as environment variables.
146
+
147
+
#### Configuration File Options
148
+
149
+
##### App Configuration (`apps` array)
150
+
151
+
| Parameter | Type | Optional | Default | CLI | Env Variable | Example | Description |
|`appId`| String | no | - |`--appId`|`PARSE_DASHBOARD_APP_ID`|`"myAppId"`| The Application ID for your Parse Server instance. |
154
+
|`masterKey`| String \| Function | no | - |`--masterKey`|`PARSE_DASHBOARD_MASTER_KEY`|`"key"`| Master key for full access. Can be a String or Function returning a String. |
155
+
|`serverURL`| String | no | - |`--serverURL`|`PARSE_DASHBOARD_SERVER_URL`|`"http://localhost:1337/parse"`| The URL where your Parse Server is running. |
156
+
|`appName`| String | yes |`appId`|`--appName`|`PARSE_DASHBOARD_APP_NAME`|`"MyApp"`| Display name of the app. |
157
+
|`masterKeyTtl`| Number | yes | - |`--masterKeyTtl`| - |`3600`| TTL for master key cache in seconds (when `masterKey` is a Function). |
|`sslKey`| String | yes | - |`--sslKey`|`PARSE_DASHBOARD_SSL_KEY`|`"/path/key"`| Path to SSL private key for HTTPS. |
242
+
|`sslCert`| String | yes | - |`--sslCert`|`PARSE_DASHBOARD_SSL_CERT`|`"/path/cert"`| Path to SSL certificate for HTTPS. |
243
+
|`cookieSessionSecret`| String | yes | Random |`--cookieSessionSecret`|`PARSE_DASHBOARD_COOKIE_SESSION_SECRET`|`"secret"`| Secret for session cookies (for multi-server). |
|`--createUser`| Interactive tool to generate secure user passwords and MFA secrets. |
253
+
|`--createMFA`| Interactive tool to generate MFA secrets for existing users. |
170
254
### File
171
255
172
256
You can also start the dashboard from the command line with a config file. To do this, create a new file called `parse-dashboard-config.json` inside your local Parse Dashboard directory hierarchy. The file should match the following format:
0 commit comments