Richard Brežák

> in which case having a referenceable specification would be a good thing! If I had to describe how I'd imagine a perfect future for this RFC and deploy-rs/yeet generally...

> Maybe rewriting it and splitting it up is the right step. Maybe we should take a step in the other direction and get rid of some extra features How...

should I expand on the proposal? I'd start with a detailed functionality description and feature set.

Cool! Can't wait honestly! Nix isnt such a bad language as some make it out to be but Nickel is definitely a solid step up.

Oh my! It's here

its not a race condition running with `RUST_LOG=trace` reveals ``` 🚀 ℹ️ [deploy] [INFO] Activating profile `system` for node `blowhole` 🚀 ❓ [deploy] [DEBUG] Constructed activation command: sudo -u root...

same here with alacritty/emacs-vterm + bash

@wucke13 when this happens a ssh process is left behind like you mention in #107 and that causes the lost input, if you kill it then everything works like normal....

So the current plan is a totally pure language with no internal effects? I'm asking because I want to take a shot at a `readFile` `getEnv` interface and without internal...

Thanks for the info, I'll try to throw something together with monads or smth, we'll see how badly it ends up working.