-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use NixOS on the production site #8
Comments
@ForNeVeR I find this experiment really interesting and I vote for it. The results of this experiment can produce pretty useful artificats (which I hope to use later on my Stream Hub, which is also on DO with Ubuntu). If you need any help from my side, feel free to ask. |
That sounds nice and I vote for this, even though I'm not interested in any of the ops stuff at the moment. Step 3 sounds like you'll abandon the idea if |
@ForNeVeR CoreOS is only good for when you want to mangle your brain with big-D containers, microservices and whatever jolly insanity happening out there in the If I understood your intent correctly, definitely do give NixOS a try. OTOH you could try something less system-invasive, like ansible, or chef |
@ForNeVeR also, i'd like to offer a donation to cover our infrastructure expenses and/or time to reconfigure our boxen. |
Nope, I didn't meant that. I'll abandon the idea if
I've already tried these, and they aren't so interesting: they won't help us to manage stuff at the level I'd want to. I am already using NixOS on one of my servers and one of my notebooks, so I think that it'll actually help.
I'll definitely let you know when your help will be useful. Currently it's just a plan, and I'm not sure if I'll have enough time and courage to implement it next week or next month. But thanks anyway, I'll keep that in mind. |
You could try Disnix, which I've been using at work during the transition from Debian GNU/Linux to NixOS. |
I have a log-standing target of using OS with declarative and reproducible configuration instead of constantly failing LTS Ubuntu that I have to mess up manually.
(And we're already messing it up much: we have some custom PPAs for GHC, Prosody and dotnet-cli, we have some custom configuration of firewall, we have fail2ban and I don't know whether it works or not, we have VPN server set up and I have no freakin' idea how to manage it all; everything is ad-hoc and undocumented, although I'm trying to keep the copies of the changed configurations in a safe place.)
So, I have the following plan:
nixos-assimilate
ornixos-in-place
on that machine.nixos-assimilate
while preserving the existing services (prosody, loglist, ctor, nginx) and documenting the experience (ideally in form of deployable config file).The text was updated successfully, but these errors were encountered: