MixRank has been using nix in production for over 3 years now. We're just using the nix package manager on Ubuntu and MacOS, not nixos. Easily one of the best technical decisions I've made.
What do you mean by: "The fork is then squashed as a git subtree into our main repo"? I don't grasp what actually happens there, between the two repos (the nixpkgs fork repo vs. your main repo)?
There are a few outstanding issues that are keeping me from using it in production but it's pretty stellar as a home system. There are a few companies using it though. Biggest issues I have at the moment relate to secrets/keys not being storable in a sensible way. That and the dev environment is in my opinion so different than the norm that it seems to break some tools like spacemacs and some embedded arm tools in my case
Yes, we use it for all our customer-facing web services at Zalora! It works as advertised and is rock-solid. I also run it on all my Linux laptops (2 personal + 1 work).
- how do you provision & manage systems/instances?
- relative to any other ways you've done this, how much effort goes into standing up the first server, any additional servers, and ongoing maintenance/management?
Also: how do you upgrade the system? Do you jump between "releases"/stable channels, or do you somehow chase the nixos-unstable channel? Do you do some kinds of pinning of nixpkgs?
[+] [-] smilliken|7 years ago|reply
Here's a comment I left on it's benefits: https://news.ycombinator.com/item?id=10714102
[+] [-] akavel|7 years ago|reply
[+] [-] qwerty456127|7 years ago|reply
[+] [-] bfrog|7 years ago|reply
[+] [-] zopa|7 years ago|reply
What's the issue with keys/secrets you've had?
[+] [-] vaibhavsagar|7 years ago|reply
[+] [-] abathur|7 years ago|reply
- how do you provision & manage systems/instances?
- relative to any other ways you've done this, how much effort goes into standing up the first server, any additional servers, and ongoing maintenance/management?
[+] [-] akavel|7 years ago|reply
[+] [-] jugmac00|7 years ago|reply