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
* Add using docker section
* Add Using Express.js section
* Add Running Parse Dashboard section
* Update _includes/graphql/getting-started.md
Co-Authored-By: Tom Fox <[email protected]>
* Removing bulleted list for single notes
* One more
* Run `parse-server --help` or refer to [Parse Server Options](https://parseplatform.org/parse-server/api/master/ParseServerOptions.html) for a complete list of Parse Server configuration options.
15
-
* ⚠️ Please do not use `--mountPlayground` option in production as anyone could access your API Playground and read or change your application's data.
15
+
* ⚠️ Please do not use `--mountPlayground` option in production as anyone could access your API Playground and read or change your application's data.[Parse Dashboard](#running-parse-dashboard) has a built-in GraphQL Playground and it is the recommended option for production apps.
16
16
17
17
After running the CLI command, you should have something like this in your terminal:
18
18
@@ -21,3 +21,76 @@ After running the CLI command, you should have something like this in your termi
21
21
Since you have already started your Parse GraphQL Server, you can now visit [http://localhost:1337/playground](http://localhost:1337/playground) in your web browser to start playing with your GraphQL API.
After starting the server, you can visit [http://localhost:1337/playground](http://localhost:1337/playground) in your browser to start playing with your GraphQL API.
38
+
39
+
⚠️ Please do not use `--mountPlayground` option in production as anyone could access your API Playground and read or change your application's data. [Parse Dashboard](#running-parse-dashboard) has a built-in GraphQL Playground and it is the recommended option for production apps.
40
+
41
+
## Using Express.js
42
+
43
+
You can also mount the GraphQL API in an Express.js application together with the REST API or solo:
app.use('/parse', parseServer.app); // (Optional) Mounts the REST API
67
+
parseGraphQLServer.applyGraphQL(app); // Mounts the GraphQL API
68
+
parseGraphQLServer.applyPlayground(app); // (Optional) Mounts the GraphQL Playground - do NOT use in Production
69
+
70
+
app.listen(1337, function() {
71
+
console.log('REST API running on http://localhost:1337/parse');
72
+
console.log('GraphQL API running on http://localhost:1337/graphql');
73
+
console.log('GraphQL Playground running on http://localhost:1337/playground');
74
+
});
75
+
```
76
+
77
+
After starting the server, you can visit [http://localhost:1337/playground](http://localhost:1337/playground) in your browser to start playing with your GraphQL API.
78
+
79
+
⚠️ Please do not mount the GraphQL Playground in production as anyone could access your API Playground and read or change your application's data. [Parse Dashboard](#running-parse-dashboard) has a built-in GraphQL Playground and it is the recommended option for production apps.
80
+
81
+
## Running Parse Dashboard
82
+
83
+
[Parse Dashboard](https://github.com/parse-community/parse-dashboard) is a standalone dashboard for managing your Parse Server apps, including your objects' schema and data, logs, jobs, and push notifications. Parse Dashboard also has a built-in GraphQL Playground that you can use to play around with your auto-generated Parse GraphQL API. It is the recommended option for production applications.
84
+
85
+
The easiest way to run the Parse Dashboard is through its CLI:
After starting the dashboard, you can visit [http://0.0.0.0:4040/apps/MyAppName/api_console/graphql](http://0.0.0.0:4040/apps/MyAppName/api_console/graphql) in your browser:
To learn more about Parse Dashboard and its setup options, please visit [Parse Dashboard Repository](https://github.com/parse-community/parse-dashboard).
0 commit comments