[1/4] feat(web): scaffold control-plane console and deploy wiring - #76
Open
immanuel-peter wants to merge 1 commit into
Open
[1/4] feat(web): scaffold control-plane console and deploy wiring#76immanuel-peter wants to merge 1 commit into
immanuel-peter wants to merge 1 commit into
Conversation
Add the Next.js app shell, shadcn UI kit, Compose/Kubernetes web service, and getting-started docs. Feature routes are stubs until later PRs in the stack land connection and resource views. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Jul 29, 2026
Contributor
|
✅ OpenCodeReview: Some files could not be reviewed due to errors. |
Collaborator
|
Thanks for your contribution! This is a huge body of work that clearly took substantial effort. Adding a WebUI could benefit AgentENV a lot. However, this series of changes adds over 50K LoC to our repo, which would significantly increase the maintenance burden. I'd suggest keeping the UI in your own repo instead, and adding a reference to it in our README or docs. What do you think? |
Author
|
That makes sense. Then, should I migrate this work to a separate |
Collaborator
|
Yes, please go ahead. Thanks! |
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
2 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.
What
Add the Next.js control-plane Web UI scaffold (
web/), Compose/Kubernetes deploy wiring foragentenv-web, and getting-started docs. Feature routes are intentional stubs until later PRs in this stack.Why
Maintainers asked for smaller reviewable PRs rather than one large Web UI change. This first slice lands deployable shell + docs without connection or resource logic.
Related issue
Part of #6 (full stack closes it via #79).
Scope and non-goals
In scope
Dockerfile.web, Composewebservice, k8s Deployment/ServiceNon-goals
Design and behavior changes
web/package (Next.js App Router + pnpm)agentenv-webCompatibility and operations
AENV_DEFAULT_GATEWAY_URLenv is present for later PRsweb/; container viadeploy/docker/Dockerfile.webValidation
Commands and results:
Skipped checks and reasons:
make fmt/make clippy/make test-unit: no Rust changes in this slicemake -C services test: no Go service code changes (deploy YAML only)Risks and reviewer notes
deploy/docker-compose.yml,deploy/docker/Dockerfile.web,deploy/k8s/base/web-*.yamlfeat/agentenv-webuion the forkStack
Please merge strictly 1 → 4. Until preceding PRs merge, later PR diffs include earlier layers; review scope for PR k after the first is its latest commit (compare link in each body). After each merge, remaining PRs will be rebased onto
main.Checklist