roberth/meta
1
0
Fork 0
forked from Fediversity/meta
Code Pull requests Activity

better explaination on NixOS

Browse source
This commit is contained in:
Koen de Jonge 2024-09-16 10:35:41 +02:00
parent 6654772100
commit d50667e391
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
Fediversity_software_stack.md
View file

@ -20,6 +20,7 @@ In our project plan we have stated that we will use Nix and NixOS for all our de
There is a number of reasons for this: There is a number of reasons for this:
* Nix promises to be fully reproducable. This will provide us with a stable way to deploy tested sets of software AND a way to revert changes easily. Debian, arch, rpm-based distri all do not provide us with this and it is of the highest importance that we do get this. * Nix promises to be fully reproducable. This will provide us with a stable way to deploy tested sets of software AND a way to revert changes easily. Debian, arch, rpm-based distri all do not provide us with this and it is of the highest importance that we do get this.
* We are helping the Nix(OS) community further, we are giving value to NixOS and are helping building it into a full competitive ecosystem.
* NixOS is 'upcoming' and 'hip' and 'happening'. The community is still not completly settled and there are tools that are still being developed and where we can actually help to develop the way things work. This will give our project value. * NixOS is 'upcoming' and 'hip' and 'happening'. The community is still not completly settled and there are tools that are still being developed and where we can actually help to develop the way things work. This will give our project value.
* NixOS does already contain examples of deployments of several tools in the Fediverse. We can use these to further our project quickly. * NixOS does already contain examples of deployments of several tools in the Fediverse. We can use these to further our project quickly.
* If we do it right, we should get the maximum available speed of developing our system, since we don't have to redo stuff after we actually fixed it (at least this is what we hope). * If we do it right, we should get the maximum available speed of developing our system, since we don't have to redo stuff after we actually fixed it (at least this is what we hope).