Conversation
Keeps a preview deployment (and its own Neon database branch) alive so a prospect can edit content while evaluating the CMS, without touching the shared demo data. No code diff from main by design - see apps/cms/SANDBOX.md. Not for merge.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Closed
Member
Author
|
Retiring this sandbox - the evaluation it was opened for is over. Closing takes the preview deployment and its Neon database branch with it, as described above. |
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
1 participant
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.
Holds open a preview deployment of
apps/cmsso a prospect can log in and edit content while they evaluate the CMS against another platform. They asked for a login they could actually try, not a walkthrough.Do not merge, and do not push code here. There is no code diff from
mainon purpose - they should see stock Ideal CMS, not a work in progress. The single file in the diff isapps/cms/SANDBOX.md, which exists so the branch explains itself and so Vercel cannot skip the build for having no changes under the project root.This repo is public, so neither the branch nor this description says which prospect it is for. The mapping and the login live in the deal record.
Why a PR at all
The open PR is what keeps the preview deployment alive, and the Neon integration gives that deployment its own database branch copied from the parent. They can create, publish and delete as much as they like without touching the shared demo data.
Known limits of the sandbox
Vercel crons run on production deployments only, so the hourly
/api/scheduled-publish/runjob does not fire here. A scheduled publish can be set up and inspected, but nothing executes it until that endpoint is called.Retiring it
Close the PR and delete the branch - the preview deployment and the Neon branch go with it.