upcast

There is Upcast[1], which is a different tool by Zalora and does this - it simply adds a file you can check into the repository for developers to use. It has some beta-ish limitations but the idea is what you described, basically. The remaining build step, then, is copying the new closure of the environment to the machine on deploy, which can take some time depending on your network. Instead I think what you'd probably do is use Hydra (a CI server) to actually build the packages/closure of your network on every commit to your repository, and then add that server to your actual deployment server's binary caches - that way when you deploy things after CI allows it, the needed assets will already be on the remote (faster) binary cache, within your network. [1] https://github.com/zalora/upcast

REMOTE - Global DevOps - Haskell and Nix We're looking for 1 more developer with systems/operations experience to join us. We are a team of 5 working to simplify and automate operations of our 7+ networks of websites and internal services across Southeast Asia. The entire team is remote. We've built and tested a Nix(OS)-based network powering a traditional LAMP stack, running on AWS. Initially deployed with NixOps, we've since started deploying it with our in-house tool written in Haskell (https://github.com/zalora/upcast). Currently in testing, it will soon be in production serving 7+ countries and 1 million+ customers. We release as much as we can under Free Software licenses and contribute upstream to open source projects when possible. We have no fixed schedules and no deadlines. Your job would be to learn your way around our infrastr