Brandon Bloom

[BUG] Ungraceful handling of port conflicts for the backend server

3

via @coderberry If the backend, gui, or syslog ports conflict, the backend fails without any good way of communicating this to the user except in the exod logs.

[FEATURE] command aliases / operation components

1

This is a tracking issue for two undeveloped feature request ideas. One is a git-like command alias system. See `git help config` and jump to `alias.*` for details. The other...

[FEATURE] Pseudo Terminal (PTY)

1

Today, we do not provide a pseudo terminal (PTY) to programs. A lot of programs detect the presence of a PTY/TTY in order to automatically enable/disable colors or similar. Also,...

**To Reproduce** 1. use `exo run 2. launch the gui 3. click to stop a process 4. you'll see a flash of an "internal server error"

Sometimes, I edit a Procfile or a docker-compose.yaml file, and forget to run `exo apply`. If I'm using `exo run`, the apply is automatic, but we should watch the current...

[FEATURE] release notes should include changelog details

1

would be nice if our release script copied the most recent changelog entries in to the release notes

**Is your feature request related to a problem? Please describe.** Typos or other errors in specs are not caught until `start` or similar lifecycle events. It would be nice to...

[FEATURE] Spec Templating

2

It's natural for some components to have customization points or other forms of dynamic configuration. A typical solution is to support environment variables (see #78) and/or some form of templating....

upgrading doesn't restart daemon

3

I think two things have to happen: 1) need to run `exo exit` if `exo` is on the path 2) the `ensureDaemon` health check should validate the version matches correctly

if component spec is invalid, create still succeeds

1

If you click "Create Process" twice in a row:   Need either/both of earlier spec validation and an "error/invalid" state for components, so that creation will succeed and the...