Repository navigation
docs: publish the Serverpod Cloud API URL and update Serverpod version references - #121
Merged
Merged
Conversation
…n references Refs #31. The root README now links the deployed API instead of a placeholder, and the health check example sends a body (Serverpod Cloud answers 411 without one). Serverpod 3.4.13 references in the server README, the CORS middleware doc and the secrets guide now say 4.0.4; preflight behavior was re-verified against production.
TOMOKI977
added
area: docs
TOMOKI977
requested review from
Pericena,
XxHugheadxX,
fercodes and
moises-cisneros
October 8, 2026 16:28
Deploying puls3 with
|
| Latest commit: |
2604ebf
|
| Status: | ⚡️ Build in progress... |
Contributor
Author
|
@moises-cisneros @fercodes @Pericena @XxHugheadxX small docs PR waiting on a review (the API URL in the root README, Serverpod 4.0.4 references). It is part of #31. Could someone take a look today? |
XxHugheadxX
approved these changes
Oct 8, 2026
XxHugheadxX
left a comment
XxHugheadxX
left a comment
Contributor
There was a problem hiding this comment.
Checked against production:
POST -d '{}' /health/checkreturns{"__className__":"BackendHealth","version":"1.0.0+4df3ba4"}.- A preflight with
Origin: https://evil.examplereturns 200 withAccess-Control-Allow-Origin: *, so the 4.0.4 note is accurate. I also confirmed this in the serverpod-4.0.4 source:_headersis injected beforeaddMiddlewareand returns early onOPTIONS. - A
POSTfrom that origin gets 403, and one fromhttps://puls3-4lw.pages.devgets 200. - Outside the openspec archive, the remaining
3.4.13references on main are the ones this PR fixes. The migration doc is the intended exception.
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #31
Docs-only follow-up to the Serverpod Cloud deploy (#117). It covers the "Both URLs are in the README" criterion. #31 stays open for the end-to-end GIF and the teammate redeploy.
Changes
README.mdpuls3-hub-on-stellar.api.serverpod.space). The health-check example sends-d '{}'(Cloud answers411without a body) and shows a sample response.puls3_server/README.mdpuls3_server/lib/src/cors/allowed_origins.dartdocs/infra/secrets.mddocs/operations/serverpod-4-migration.mdstill mentions 3.4.13 on purpose: that line is the rollback step.Verification
curl -s -X POST -d '{}' https://puls3-hub-on-stellar.api.serverpod.space/health/checkreturns{"__className__":"BackendHealth","version":"1.0.0+4df3ba4"}.OPTIONSpreflight against production on 4.0.4 still returnsAccess-Control-Allow-Origin: *, so the CORS note stays accurate.