11 commits

Author	SHA1	Message	Date
Eelco Dolstra	c20c082383	<envar> -> <literal>	2020-07-23 18:27:11 +02:00
Niklas Hambüchen	caa76c369a	docs: Mention --max-jobs 0 to build remotely only	2019-03-31 03:57:45 +02:00
Joachim Breitner	684c7fff80	Link to builders-use-substitutes in chapter on distributed builds ... fixes #2730.	2019-03-16 19:03:40 +01:00
Niklas Hambüchen	10ebcf8670	manual: distributed-builds: Mention - as default	2018-06-17 19:01:07 +02:00
Eelco Dolstra	0d54671b7b	Manual: Update chapter on remote builds ... Alos add a command "nix ping-store" to make it easier to see if Nix can connect to a remote builder (e.g. 'nix ping-store --store ssh://mac').	2018-02-21 16:24:26 +01:00
Eelco Dolstra	d7653dfc6d	Remove $NIX_BUILD_HOOK and $NIX_CURRENT_LOAD ... This is to simplify remote build configuration. These environment variables predate nix.conf. The build hook now has a sensible default (namely build-remote). The current load is kept in the Nix state directory now.	2017-05-01 17:30:16 +02:00
Shea Levy	418a837897	Remove perl dependency. ... Fixes #341	2017-02-07 15:56:32 -05:00
Domen Kožar	9a1320af29	s/powerpc-darwin/x86_64-darwin/ ... Let's step in line with time and document more realistic values.	2016-08-10 18:42:55 +02:00
Eelco Dolstra	77c2739c25	Grammar/spelling	2016-07-21 11:30:01 +02:00
Matthias Beyer	2ec9d2fb02	NIX_REMOTE_SYSTEMS path must be absolute (#957) ... Once upon a time, I wrote my bachelors thesis about functional deployment mechanisms. I had to evaluate several szenarios where package management and deployment were relevant. One szenario was to do distributed builds over several machines. I told myself: Weee, nix can do this! And with nix, this is actually save, as you do not have side effects when building! So I started. I use a cloud to set up four virtual machines where I wanted to do the build. A fifth machine was used as master to distribute the builds. All was good. I created the necessary SSH keys, made sure every machine was reachable by the master and configured the build in my remotes.conf. When I started to try to build weechat from source, the build failed. It failed, telling me error: unable to start any build; either increase ‘--max-jobs’ or enable distributed builds And I started to dig around. I digged long and good. But I wasn't able to find the issue. I double and triple checked my environment variables, my settings, the SSH key and everything. I reached out to fellow Nixers by asking on the nixos IRC channel. And I got help. But we weren't able to find the issue, either. So I became frustrated. I re-did all the environment variables. And suddenly,... it worked! What did I change? Well... I made the environment variables which contained pathes contain absolute pathes rather than relatives. And because I like to share my knowledge, this should be put into the documentation, so others do not bang their heads against the wall because something is not documented somewhere.	2016-07-21 11:19:21 +02:00
Eelco Dolstra	9c830394ec	Rename files	2014-12-14 01:07:23 +01:00

Renamed from doc/manual/builds/enabling-builds.xml (Browse further)