Hacker News Reader

This seems to be at the same level of how Meta manages their dev environments. You pick the environment right from VS code and it spins up an environment.

I think

> Add multi-node support

will be important for non trivial project development where the 2 distinct environments might be needed to talk to each other like say for prototyping or "sharing configs"..

View on HN

By multi-node support we mean the ability of Hocus to manage multiple machines, so you can run dev envs on more than one server and handle more concurrent users. These environments would not communicate with one another. From the end user's perspective using a multi-node deployment vs a single-node deployment would not differ. If you needed 2 distinct environments I would suggest using virtualization within a single dev env.

Reply on news.ycombinator.com