Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
The admin content loader parses HTML as JSON when its API URL reaches a frontend or misrouted proxy. Service diagnostics also accept any HTTP 200 as healthy, so the UI can report services online while content loading fails.
This change defaults local development to a loopback Vite /api proxy targeting the private Node server on port 8787, while preserving explicit API URL overrides. It validates JSON responses and the content payload, adds a 10-second content timeout, and loads the bundled portfolio snapshot when the content API is unavailable. Loading no longer deletes existing recovery drafts. Service checks validate the expected service/configuration fields; AI status explicitly reports configuration rather than verified availability.
Setup: existing admin/.env API overrides must be cleared to use the development proxy. Remote private APIs can use ADMIN_PROXY_TARGET. See docs/admin-connection.md for local and production setup. Vercel remains the public-services API and is not used for admin writes.
Validation: admin production build passed; four Node regression tests passed; live Vite proxy checks passed for an unavailable backend (JSON 502) and a mock available backend (JSON forwarding). No credentials or user content changed. Actual private/Tailscale services were not accessible for end-to-end verification. Nothing has been merged or deployed.