Restore historical Command Center shell - #39
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f907f20d5b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| </div> | ||
| </article> | ||
|
|
||
| <p class="platform-note">Private links use the local loopback address and become available only through your authenticated SSH tunnel. This directory does not claim live health.</p> |
There was a problem hiding this comment.
Provide the SSH command required by private links
The five private destinations point at the visitor's loopback interface, but this deployed snapshot only says that a tunnel is required and provides no way to establish it. builder/deploy_to_scripts.sh copies this file to the runtime location, and DashboardHandler.translate_path() serves it for /, so users arriving at the restored shell cannot use those links unless they already know every required port forward. Preserve the copyable all-ports tunnel command already shown in the generated Common Center snapshot.
Useful? React with 👍 / 👎.
Project update: Historical Command Center restored on OVHStatus: Restored the historical Hello, Maxim Command Center shell at command.meshly.fr, preserved Mac Mini/Air/Pro/Agents, added the seven-platform directory, deployed the static Campus surface, and created an isolated Cloudflare tunnel without changing the existing MyDictionary tunnel. Evidence
Next
|
Summary
Verification