What happens after you cut a release? Getting your finished software in the hands of your users can be quite an ordeal, especially if you use tools that make things harder than they need to be. It turns out that a functional approach has benefits even after the development team has written their last line of code.
I will motivate and demonstrate using the Nix suite of tools to package and deploy a web service, showing how this helps us reconcile the sometimes conflicting priorities of development and operations teams and allows us to respond nimbly to change as it occurs.
I hope to leave you with the assurance that Nix is production-ready and the means to start using it yourself.
After getting frustrated with the state of web development and watching his friends rave about lenses and monads, Vaibhav decided that functional programming was the solution to all his problems and took some time off to attend a batch at the Recurse Center, where he tried to get his head around this Haskell thing by reimplementing Git in it. Now he talks about applicatives and content-addressable stores at parties and animates servers with Nix for a living.