Skip to content

Commit 3ab7038

Browse files
funkenstrahlendrew-gross
authored andcommitted
syntax highlight json files in readme (#287)
1 parent 51b6c08 commit 3ab7038

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

README.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ You can then visit the dashboard in your browser at http://localhost:4040. You m
2323

2424
If you want to manage multiple apps from the same dashboard, you can start the dashboard with a config file. For example, you could put your info into a file called `parse-dashboard-config.json` and then start the dashboard using `parse-dashboard --config parse-dashboard-config.json`. The file should match the following format:
2525

26-
```
26+
```json
2727
{
2828
"apps": [
2929
{
@@ -38,7 +38,7 @@ If you want to manage multiple apps from the same dashboard, you can start the d
3838

3939
You can also manage apps that on 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`:
4040

41-
```
41+
```json
4242
{
4343
"apps": [
4444
{
@@ -62,7 +62,7 @@ You can also manage apps that on Parse.com from the same dashboard. In your conf
6262

6363
Parse Dashboard also supports adding an optional icon for each app, so you can identify them easier in the list. To do so, you *must* use the configuration file, define an `iconsFolder` in it, and define the `iconName` parameter for each app (including the extension). The path of the `iconsFolder` is relative to the configuration file. To visualize what it means, in the following example `icons` is a directory located under the same directory as the configuration file:
6464

65-
```
65+
```json
6666
{
6767
"apps": [
6868
{
@@ -90,7 +90,8 @@ You can set `appNameForURL` in the config file for each app to control the url o
9090
Make sure the server URLs for your apps can be accessed by your browser. If you are deploying the dashboard, then `localhost` urls will not work.
9191

9292
In order to securely deploy the dashboard without leaking your apps master key, you will need to use HTTPS and Basic Auth. You can do this by adding usernames and passwords for HTTP Basic Auth to your configuration file.
93-
```
93+
94+
```json
9495
{
9596
"apps": [...],
9697
"users": [
@@ -112,7 +113,7 @@ The deployed dashboard detects if you are using a secure connection. If you are
112113

113114
If you want to restrict apps based on user identity, you can update your config file to match the following format:
114115

115-
```
116+
```json
116117
{
117118
"apps": [ ],
118119
"users": [

0 commit comments

Comments
 (0)