From d0608da13fa8e95e92c45e6f77a99731177d5d0c Mon Sep 17 00:00:00 2001 From: Eelco Dolstra Date: Tue, 16 Sep 2014 14:36:32 +0200 Subject: [PATCH] Drop "service deployment" bla bla --- doc/manual/introduction/about-nix.xml | 30 +-------------------------- 1 file changed, 1 insertion(+), 29 deletions(-) diff --git a/doc/manual/introduction/about-nix.xml b/doc/manual/introduction/about-nix.xml index e45a32d21..0346934b0 100644 --- a/doc/manual/introduction/about-nix.xml +++ b/doc/manual/introduction/about-nix.xml @@ -80,11 +80,6 @@ package won’t be built or downloaded a second time. At the same time, it is not possible for one user to inject a Trojan horse into a package that might be used by another user. - - @@ -198,33 +193,10 @@ collection (Nixpkgs). -Service deployment - -Nix can be used not only for rolling out packages, but also -complete configurations of services. This is -done by treating all the static bits of a service (such as software -packages, configuration files, control scripts, static web pages, -etc.) as “packages” that can be built by Nix expressions. As a -result, all the features above apply to services as well: for -instance, you can roll back a web server configuration if a -configuration change turns out to be undesirable, you can easily have -multiple instances of a service (e.g., a test and production server), -and because the whole service is built in a purely functional way from -a Nix expression, it is repeatable so you can easily reproduce the -service on another machine. - - - - - - Portability Nix should run on most Unix systems, including Linux and Mac OS -X. +X.