-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
Document the status of the project #1545
Comments
@roberth @adisbladis @grahamc : according to the commit history, you are the most recently involved people. Do you still use NixOps? |
I do and I plan to make a maintenance push soon. |
Where would the maintenance push be when it is made? I see no tags since 2019. I see three active branches, but those are for NixOps 2, which is still unstable if I understand correctly. |
I wonder what is the status of 2.0. I use nixops to deploy my vps. up to this point there were not really any critical things that made me worried but now I will need to host something that will have DB and will hold some bit more sensitive data so I'm faced with dilema what to do about it. |
Planning to merge #1508 and a rebase of #1523 or #1480 in the coming two weeks. That should bring a 2.0 release candidate within reach. If you can fund development and maintenance, or know someone, that can speed things up. |
Hey any updates on the status of this project? I just started getting my hands deep with Nix and NixOS and I was trying to use NixOps to deploy my flakes that I have been building, but alas I find out that NixOps 2.0 does not have flake support as of yet. I checked the PRs and I don't see the critical flake attribute related ones being closed, so I am unsure whether I can simply build NixOps from master and try out deployments via flakes. Fairly conflicted between supporting NixOps which seems perfect for the job. Or switching to some other terraform like system for lab automation, which wouldn't be as idiomatic and compatible as Nix default tools. 😄 |
Fixed in 3f8249a |
Here are a few facts about
nixops
:nixops
does not have a stable release working without disabling security warnings (Request: Release 1.7.1 with security patch for CVE-2022-29217 #1532)Yet,
nixops
is very useful to me. However, I have come to a point where I am not sure I should invest more time trying to open issues or even usenixops
since it feels like wasted efforts. The project may be abandoned, I do not know and it is not documented anywhere.I understand that there is limited resource but I think a clear and updated project status would incentive participation (or stop it right away). A small paragraph in the README.md would be a good start.
The text was updated successfully, but these errors were encountered: