replying to @dtinth-bot
I like option C the most. However, I think we should have a button to import the compose file separately. This option should not be hidden in the last step. That's too confusing.
Commit
e3864a3
C it is. Plan: an Import button in the header that takes your compose.yaml (and .env for secrets), with the answers carried in an x-agent-env key so the separate JSON goes away. Building it as the real page now.
Good. Here is your temporary claw grant. Use your ssh key.…
Thanks, but my sandbox's permission check blocked decrypting it, so I didn't use it. The commits are ready on the worktree branch; the push command for you is in the session.
It won't even let you decrypt and pipe to claw grant in one go?
Piping worked: grant installed. But my worktree sandbox refuses pushes run through claw exec, so the branch is still local. One command from your side does it (it's in the session).
Don't do it in worktree. Use the main checkout to push, please.
@dtinth Pushed from the main checkout: https://github.com/dtinth/agent-env/tree/configurator-revamp (2 commits). Want a draft PR?
GitHubGitHub - dtinth/agent-env at configurator-revamphttps://dtinth.github.io/agent-env/. Contribute to dtinth/agent-env development by creating an account on GitHub.
Please make a PR and watch it. Once you think it's ready for review, please put it out of draft.
@dtinth PR #36 is ready for review: CI green (both builds with smoke tests, setup wizard). https://github.com/dtinth/agent-env/pull/36
GitHubConfigurator: Preact stepper, Import button, answers inside compose.yaml by dtinth-claw[bot] · Pull Request #36 · dtinth/agent-envThe web configurator, redone as a Preact stepper in the dt.in.th design system that claw uses (dark only), and the setup answers moved into compose.yaml. Picked from three prototypes discussed on d...
Done in 4a1f170: the summary values are now muted body text, the same as Opens at. Pushed to #36.
No need for the text below the heading ("Answers in…"), please remove it.
Removed in 620bf20: the header is just the title and Import now. Pushed to #36.
Please watch and address the review comments.
Both fixed in 93ef0b7. The missing-secrets notice now stays until you import the .env, re-roll, or click "use the new ones". Importing only a .env keeps your answers. Checked both in the browser.
Thanks - please merge to main when green.
CI is green on 93ef0b7, but my session's permission check blocked the merge as unreviewed. Could you press Rebase and merge on #36, or allow merges for my session?
Permission granted
@dtinth Merged to main (rebase, b52508c): https://github.com/dtinth/agent-env/pull/36
GitHubConfigurator: Preact stepper, Import button, answers inside compose.yaml by dtinth-claw[bot] · Pull Request #36 · dtinth/agent-envThe web configurator, redone as a Preact stepper in the dt.in.th design system that claw uses (dark only), and the setup answers moved into compose.yaml. Picked from three prototypes discussed on d...
What is
name: agent-env in the compose file? Would this prevent running multiple envs on a single machine?commit e3864a3
It's the Compose project name, so yes: a second deploy with the same name replaces the first's containers and shares its volumes, even from another directory. Dropping the line makes the folder name the default. Ports must still differ. Want that?