Brennen Bearnes 5 years ago
parent
commit
eeeb80588b
1 changed files with 2 additions and 2 deletions
  1. +2
    -2
      README.md

+ 2
- 2
README.md View File

@ -566,7 +566,7 @@ curl -X POST \
Since `curl` sends GET requests by default, and we're not supplying any data, you should only need to send the Application ID in order to read some sample data back:
```command
curl -H "X-Parse-Application-Id: <^>your_application_id<^>" https://p1k3.com/parse/classes/GameScore
curl -H "X-Parse-Application-Id: <^>your_application_id<^>" https://<^>your_domain_name<^>/parse/classes/GameScore
```
```
@ -613,7 +613,7 @@ Your app should now be migrated.
## Conclusion and Next Steps
This guide offers a functional starting point for migrating a Parse-hosted app to a Parse Server install on a single Ubuntu system, such as a DigitalOcean droplet. The configuration we've described should be adequate for a low-traffic app with a modest userbase. Hosting for a larger app may require multiple systems to provide redundant data storage and load balancing between API endpoints. Even small projects are likely to involve infrastructure considerations that are not addressed directly by this document.
This guide offers a functional starting point for migrating a Parse-hosted app to a Parse Server install on a single Ubuntu system, such as a DigitalOcean droplet. The configuration we've described should be adequate for a low-traffic app with a modest userbase. Hosting for a larger app may require multiple systems to provide redundant data storage and load balancing between API endpoints. Even small projects are likely to involve infrastructure considerations that we haven't directly addressed.
In addition to reading the official Parse Server documentation and tracking the [GitHub issues for the project](https://github.com/ParsePlatform/parse-server/issues) when troubleshooting, you may wish to explore the following topics:


Loading…
Cancel
Save