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
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -102,7 +102,7 @@ Managing multiple apps from the same dashboard is also possible. Simply add add
102
102
103
103
You can manage self-hosted [Parse Server](https://github.com/ParsePlatform/parse-server) apps, *and* apps that are hosted on [Parse.com](http://parse.com/) from the same dashboard. In your config file, you will need to add the `restKey` and `javascriptKey` as well as the other paramaters, which you can find on `dashboard.parse.com`. Set the serverURL to `http://api.parse.com/1`:
104
104
105
-
```js
105
+
```json
106
106
{
107
107
"apps": [
108
108
{
@@ -153,7 +153,7 @@ To change the app to production, simply set `production` to `true` in your confi
153
153
154
154
Instead of starting Parse Dashboard with the CLI, you can also run it as an [express](https://github.com/expressjs/express) middleware.
155
155
156
-
```
156
+
```javascript
157
157
var express =require('express');
158
158
var ParseDashboard =require('parse-dashboard');
159
159
@@ -179,7 +179,7 @@ httpServer.listen(4040);
179
179
180
180
If you want to run both [Parse Server](https://github.com/ParsePlatform/parse-server) and Parse Dashboard on the same server/port, you can run them both as express middleware:
181
181
182
-
```
182
+
```javascript
183
183
var express =require('express');
184
184
var ParseServer =require('parse-server').ParseServer;
185
185
var ParseDashboard =require('parse-dashboard');
@@ -217,7 +217,7 @@ In order to securely deploy the dashboard without leaking your apps master key,
217
217
218
218
The deployed dashboard detects if you are using a secure connection. If you are deploying the dashboard behind a load balancer or front-facing proxy, then the app won't be able to detect that the connection is secure. In this case, you can start the dashboard with the `--trustProxy=1` option (or set the PARSE_DASHBOARD_TRUST_PROXY config var to 1) to rely on the X-Forwarded-* headers for the client's connection security. This is useful for hosting on services like Heroku, where you can trust the provided proxy headers to correctly determine whether you're using HTTP or HTTPS. You can also turn on this setting when using the dashboard as [express](https://github.com/expressjs/express) middleware:
219
219
220
-
```
220
+
```javascript
221
221
var trustProxy =true;
222
222
var dashboard =newParseDashboard({
223
223
"apps": [
@@ -302,7 +302,7 @@ Start your `parse-server` with
0 commit comments