fix(self-host): make first boot observable and retryable - #157
Open
tnunamak wants to merge 2 commits into
Open
Conversation
Record the terminal onboarding, bootstrap credential, recovery, and cold-start readiness requirements for standalone Core deployments. Assisted-by: AI Signed-off-by: Tim Nunamaker <tnunamak@gmail.com>
A new Core container could show a generic proxy error while its internal services were still starting, and the generated owner password was easy to miss because the Docker command did not follow the container logs. The console's selected dark theme also did not reach the hosted owner login page. Publish an explicit readiness marker after both reference services accept connections, serve a retrying startup page before that marker, and preserve a diagnostic JSON error for failures after startup. Make the local Docker command loopback-only, restart-safe, and log-following. Make Compose generate secrets with a private env file and print the owner password after startup. Mirror the console theme preference to hosted login pages. Remove the Core-incompatible one-command CLI entry from Connect apps rather than advertising a flow that fails on a standard Core deployment. Assisted-by: AI Signed-off-by: Tim Nunamaker <tnunamak@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Why
A new Core container could return a generic error while its internal services were still starting. The generated owner password was also easy to miss because the Docker command returned only a container ID. The console's dark-mode choice did not reach the hosted owner login page. The Connect apps page also showed a one-command CLI setup that does not complete on a standard Core deployment.
What changed
.env, start the stack, and print the generated owner password after startup.Verification
git diff --check: passed.data-theme="dark", Sources/Add rendered ChatGPT, the ChatGPT setup page returned 200, and unauthenticated MCP returned 401.Scope
This does not add a password-change page; deployment configuration remains the password rotation path. It does not make the standard Core
pdpp connectcommand work; the misleading dashboard row is removed instead. Hosted ChatGPT and Claude.ai still require a public HTTPS MCP endpoint; localhost is for local clients.The public self-host page will use the new command after this PR is merged and the site deploy completes.
Assisted-by: AI