Andrei Dziahel

@ellie did you try to hook to [`command_not_found`](https://www.nushell.sh/book/hooks.html#command-not-found-hook-in-arch-linux)? Sure it's a hack, but still a way to get them really dynamic. Or you could just settle with bunch of `alias`es...

I wonder why the cache is still not up, especially since it's apparently cheap, isn't it?

> On x86: Building from source takes a while. 5 minutes is a while. 30 minutes on a single CPU (with other 23 idling) is, um, huge.

Hey @deemp thank you for looking into the issue; we've phased c-n-a out for our CI setup because caching nix store was actually slower than downloading artifacts from cache.nix.org.

> Indeed, the run times with and without caching are similar. I mean, they could be better on real hardware or with more generous CPU and I/O quota for GA...

> One of them is listening on ipv4, the other on ipv6. Generally, a user expects us to stick to one protocol, right? Meanwhile, one way to reduce confusion would...

The problem here is the app server binds to `[::1]:3000` and admin server binds to `127.0.0.1:3000` because `bindPortTCP` binds to whatever address available and `localhost` resolves in both `[::1]` and...

Okay, we actually do diagnostic messages `"[Admin server] listening on port "`, but in the case of the port conflict neither of those is shown before the runtime error.

So, to summarize: * an `admin-server-host` setting should be introduced, defaulting to `server-host` value * we have to make sure the host & port of both app and admin servers...

Closing this in favor of #3559