depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2019-05-12	diff hook: execute as the build user, and pass the temp dir	Graham Christensen	1	-7/+5

2019-05-12	build: run diff-hook under --check and document diff-hook	Graham Christensen	2	-0/+208

2019-03-31	docs: Mention `--max-jobs 0` to build remotely only	Niklas Hambüchen	1	-0/+3

2019-03-16	Link to `builders-use-substitutes` in chapter on distributed builds	Joachim Breitner	1	-0/+4
	fixes #2730.
2018-09-01	Merge pull request #2237 from nh2/patch-1	Eelco Dolstra	1	-0/+1
	manual: distributed-builds: Mention - as default
2018-08-31	docs: Add IDs to important sections	Graham Christensen	1	-0/+1

2018-06-17	manual: distributed-builds: Mention - as default	Niklas Hambüchen	1	-0/+1

2018-02-21	Manual: Update chapter on remote builds	Eelco Dolstra	1	-67/+144
	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').
2017-05-01	Remove $NIX_BUILD_HOOK and $NIX_CURRENT_LOAD	Eelco Dolstra	1	-13/+2
	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-02-07	Remove perl dependency.	Shea Levy	1	-5/+5
	Fixes #341
2016-08-10	s/powerpc-darwin/x86_64-darwin/	Domen Kožar	1	-4/+4
	Let's step in line with time and document more realistic values.
2016-07-21	Grammar/spelling	Eelco Dolstra	1	-2/+2

2016-07-21	NIX_REMOTE_SYSTEMS path must be absolute (#957)	Matthias Beyer	1	-1/+2
	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.
2014-12-14	Rename files	Eelco Dolstra	2	-0/+125