Commit

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/36dtinth/agent-env#36

What is name: agent-env in the compose file? Would this prevent running multiple envs on a single machine?

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?

Yes. I think we should allow configuring the environment name. This will impact the hostname of the container too so when not using Tailscale the shell prompt looks nice. Default agent-env.

https://github.com/dtinth/agent-env/pull/37dtinth/agent-env#37 The name is asked first, defaults to agent-env, and sets both the Compose project and the hostname (under Tailscale the sidecar's hostname applies instead). CI is running.

Why https port detault to 8443? Can it be 443 instead? Also for public domain, is it possible to make it support shortlived Let's Encrypt IP certs? Alternatives are nip and sslip.

IP certs: yes. Caddy gets one with the IP as the site address and profile shortlived; I still have to check our image has that fix. Google sign-in may refuse an IP redirect URI. sslip.io/nip.io names already work. Put 443 + IP mode in #37, or a new PR?

Put in same PR pls.

@dtinth Pushed to https://github.com/dtinth/agent-env/pull/37dtinth/agent-env#37: None mode (expose only), IPv4 certs via profile shortlived (Google refused for an IP, sslip.io suggested), 443 default. CI running.

I want to ask for a new feature in the configurator: Allow specifying memory limit. Not sure how to deal with swap too. And maybe CPU limits too. Also need advice if disk quota or limit is possible and what are the possible ways to do it. These are advanced optional features tho.

Ways, easiest first: a ZFS dataset with quota=50G, or btrfs qgroups, if the host has one; else a loop-mounted ext4 image (fallocate, mkfs, mount, plus fstab). Then use host-directory mode for both. Want the page to print those commands?

Let's talk about disk later, let's do RAM and CPU first.

RAM and CPU are already in: https://github.com/dtinth/agent-env/commit/2ef225718e35758eff0b53b5718051f1ab7593ffdtinth/agent-env@2ef2257. GitHub missed the push, so #37 still shows a71ffd4 and CI hasn't run. Closing and reopening #37 should fix it. Can you do that, or should I?

37 is already merged yesterday. Need a new PR I think

Right, sorry. New PR with just the limits, on top of main: https://github.com/dtinth/agent-env/pull/38dtinth/agent-env#38. Checks and tests pass locally; CI is running.

Watch review comments too.