Skip to content

Commit fb9c19d

Browse files
committed
Update README.md
1 parent bee5b4b commit fb9c19d

File tree

1 file changed

+2
-12
lines changed

1 file changed

+2
-12
lines changed

README.md

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -106,21 +106,11 @@ If you are not familiar with Docker, ``--port 8080`` with be passed in as argume
106106

107107
## Deploying in production
108108

109-
For production deployments, it's recommended to use the npm package
110-
111-
1. Create a folder for your project
112-
2. run `$ npm init`
113-
3. Create your dashboard.json in the root ot your project
114-
4. run `$ npm install --save parse-dashboard`
115-
5. add a start script in your package.json `"start": "parse-dashboard --config ./dashboard.json"` 
116-
6. run `$ npm start`
117-
118-
119-
If you're deploying to a provider like Heroku, or Google App Engine, the SSL endpoint is terminated early and handled by the provider and you may encounter this error `Parse Dashboard can only be remotely accessed via HTTPS`.
109+
If you're deploying to a provider like Heroku, or Google App Engine, the SSL endpoint is terminated early and handled by the provider and you may encounter this error: `Parse Dashboard can only be remotely accessed via HTTPS`.
120110

121111
:warning: :warning: Before going further, make sure your server **cannot** be reachable via **HTTP**. See the provider documentation for force HTTPS connections to your deployment.
122112

123-
Set the environment variable to PARSE_DASHBOARD_ALLOW_INSECURE_HTTP=1 to tell parse server to skip the secure tests.
113+
Set the environment variable `PARSE_DASHBOARD_ALLOW_INSECURE_HTTP=1` to tell parse server to skip the secure tests.
124114

125115
To start your server use:
126116

0 commit comments

Comments
 (0)