docs: update Parse Server API links

[jacog2]

What changed

• Updates the /parse-server/api/ redirect to the active Parse Server API docs host.
• Updates Parse Server option links in the docs from parseplatform.org/parse-server/api/... to website.parseplatform.org/parse-server/api/....

Why

https://parseplatform.org/parse-server/api/ currently returns 404, while the same API documentation is available under https://website.parseplatform.org/parse-server/api/. This keeps the docs redirect and inline API links usable.

Related to #889 and parse-community/parse-server#10460.

Validation

• git diff --check
• rg -n "https?://parseplatform\\.org/parse-server/api" _config.yml parse-server-api.md _includes -S returns no matches
• Verified these URLs return HTTP 200:
  • https://website.parseplatform.org/parse-server/api/
  • https://website.parseplatform.org/parse-server/api/master/ParseServerOptions.html
  • https://website.parseplatform.org/parse-server/api/5.2.0/ParseServerOptions.html

Summary by CodeRabbit

• Documentation
  • Updated Parse Server API documentation links across configuration files and multiple setup guides including Dart, Flutter, and GraphQL.
  • Enhanced Parse Server documentation references for deployment on AWS Ubuntu, including CORS header configuration guidance.
  • Refreshed documentation links to ensure users access current Parse Server configuration and API reference materials.

[coderabbitai]

Warning

Rate limit exceeded

@jacog2 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 55 minutes and 16 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4e5efd2c-e206-497f-b8aa-d3bae59324ff

📥 Commits

Reviewing files that changed from the base of the PR and between 4bbcf9e and dde39a2.

📒 Files selected for processing (1)

• _includes/parse-server/deploying-aws-ubuntu.md

📝 Walkthrough

Walkthrough

This PR updates all Parse Server API documentation links across the site from parseplatform.org to website.parseplatform.org. The changes include site configuration, redirect pages, and documentation files for Dart, Flutter, GraphQL, and deployment guides. Dart and Flutter guides additionally include Docker-specific CORS header configuration examples.

Changes

Parse Server Documentation Domain Migration

Layer / File(s)	Summary
Site Configuration and Redirect _config.yml, parse-server-api.md	Central configuration updates apis.parse-server URL and redirect page target to website.parseplatform.org domain.
SDK Getting-Started Guides _includes/dart/getting-started.md, _includes/flutter/getting-started.md, _includes/graphql/getting-started.md	Parse Server API documentation links updated to website.parseplatform.org. Dart and Flutter guides add Docker environment variable example PARSE_SERVER_ALLOW_HEADERS=X-Parse-Installation-Id for CORS header configuration.
Integration and Deployment Guides _includes/parse-server/deploying-aws-ubuntu.md, _includes/parse-server/usage.md	Parse Server API reference links updated to website.parseplatform.org.

---

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 6 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Engage In Review Feedback	⚠️ Warning	Feedback on line 120 grammar ("This are" → "These are") not addressed and no discussion with reviewer occurred.	Either implement the proposed grammar fix on line 120 or engage with the reviewer about this feedback.

✅ Passed checks (6 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: update Parse Server API links' begins with the 'docs:' prefix, follows the required convention, and accurately describes the main changeset of updating documentation links.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Security Check	✅ Passed	No security vulnerabilities detected. URL updates use HTTPS, are hard-coded with no injection vectors, stay within same domain family, and pass all validation checks.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@_includes/parse-server/deploying-aws-ubuntu.md`:
- Line 120: The sentence "This are the basic options of the config.json file..."
has incorrect grammar; update it to "These are the basic options of the
config.json file, for the full list you can type `parse-server --help` or refer
to the full options document..." so replace "This are" with "These are" in the
documentation line in _includes/parse-server/deploying-aws-ubuntu.md to fix the
grammar and keep the rest of the sentence unchanged.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bfa27413-8a8f-42a1-9a8a-9434045afeda

📥 Commits

Reviewing files that changed from the base of the PR and between 51c5175 and 4bbcf9e.

📒 Files selected for processing (7)

• _config.yml
• _includes/dart/getting-started.md
• _includes/flutter/getting-started.md
• _includes/graphql/getting-started.md
• _includes/parse-server/deploying-aws-ubuntu.md
• _includes/parse-server/usage.md
• parse-server-api.md

[jacog2]

Addressed CodeRabbit's grammar suggestion in dde39a2 and re-ran validation:

• git diff --check
• rg -n "https?://parseplatform\\.org/parse-server/api" _config.yml parse-server-api.md _includes -S returns no matches
• Re-verified the replacement API URLs return HTTP 200