Skip to content

Commit 91bcb24

Browse files
committed
PR Feedback
1 parent 2130d38 commit 91bcb24

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

README.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -142,7 +142,9 @@ The hosted version of Parse will be fully retired on January 28th, 2017. If you
142142

143143
## Configuration
144144

145-
Parse Server can be configured using the following options. You may pass these as parameters when running a standalone `parse-server`. Alternatively, you can use the `PARSE_SERVER_OPTIONS` environment variable set to the JSON of your configuration, If you're using Parse Server on Express, you may also pass these to the `ParseServer` object as options.
145+
Parse Server can be configured using the following options. You may pass these as parameters when running a standalone `parse-server`, or by loading a configuration file in JSON format using `parse-server path/to/configuration.json`. If you're using Parse Server on Express, you may also pass these to the `ParseServer` object as options.
146+
147+
For the full list of configuration options, run `parse-server --help`.
146148

147149
#### Basic options
148150

@@ -174,12 +176,6 @@ The client keys used with Parse are no longer necessary with Parse Server. If yo
174176
* `allowClientClassCreation` - Set to false to disable client class creation. Defaults to true.
175177
* `oauth` - Used to configure support for [3rd party authentication](https://github.com/ParsePlatform/parse-server/wiki/Parse-Server-Guide#oauth).
176178

177-
### Using a JSON file to configure Parse Server
178-
179-
The standalone API server supports loading a configuration file in JSON format:
180-
181-
```
182-
$ parse-server path/to/your/config.json
183179
```
184180
185181
### Using environment variables to configure Parse Server

0 commit comments

Comments
 (0)