Skip to content

Commit bf228a9

Browse files
jlpiedrahitanatanrolnik
authored andcommitted
Enable JavaScript syntax highlighting in README (#809)
1 parent 35141d9 commit bf228a9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ Managing multiple apps from the same dashboard is also possible. Simply add add
102102

103103
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`:
104104

105-
```js
105+
```json
106106
{
107107
"apps": [
108108
{
@@ -153,7 +153,7 @@ To change the app to production, simply set `production` to `true` in your confi
153153

154154
Instead of starting Parse Dashboard with the CLI, you can also run it as an [express](https://github.com/expressjs/express) middleware.
155155

156-
```
156+
```javascript
157157
var express = require('express');
158158
var ParseDashboard = require('parse-dashboard');
159159

@@ -179,7 +179,7 @@ httpServer.listen(4040);
179179

180180
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:
181181

182-
```
182+
```javascript
183183
var express = require('express');
184184
var ParseServer = require('parse-server').ParseServer;
185185
var ParseDashboard = require('parse-dashboard');
@@ -217,7 +217,7 @@ In order to securely deploy the dashboard without leaking your apps master key,
217217

218218
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:
219219

220-
```
220+
```javascript
221221
var trustProxy = true;
222222
var dashboard = new ParseDashboard({
223223
"apps": [
@@ -302,7 +302,7 @@ Start your `parse-server` with
302302

303303
Then in your dashboard configuration:
304304

305-
```
305+
```javascript
306306
var trustProxy = true;
307307
var dashboard = new ParseDashboard({
308308
"apps": [

0 commit comments

Comments
 (0)