depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2019-08-05	feat(build): Build Nixery book and embed it into Nixery image	Vincent Ambo	1	-8/+10
	Executes the previously added mdBook on the previously added book source to yield a directory that can be served by Nixery on its index page. This is one of those 'I <3 Nix' things due to how easy it is to do.
2019-08-05	feat(build): Add mdBook 0.3.1 to build environment	Vincent Ambo	1	-0/+18
	Upstream nixpkgs currently only has an older versin of mdBook. Until that changes, we keep a different version in here.
2019-08-04	feat(build): Support additional pre-launch commands in image	Vincent Ambo	1	-1/+4
	This makes it possible for users to hook basically arbitrary things into the Nixery container image.
2019-08-02	docs: Update all nixery.appspot.com references to nixery.dev	Vincent Ambo	1	-2/+2
	Shiny, new domain is much better and eliminates the TLS redirect issue because there is a HSTS preload for the entire .dev TLD (which, by the way, is awesome!)
2019-08-02	fix(build): coreutils are still required by launch script	Vincent Ambo	1	-0/+1
	Mea culpa!
2019-07-31	feat(build): Add dependencies for custom repo clones	Vincent Ambo	1	-4/+4
	Adds git & SSH as part of the Nixery image, which are required to use Nix's builtins.fetchGit. The dependency on interactive tools is dropped, as it was only required during development when debugging the image building process itself.
2019-07-26	fix(build): Specify default command for Nixery's own image	Vincent Ambo	1	-0/+1
	When running on AppEngine, the image is expected to be configured with a default entry point / command. This sets the command to the wrapper script, so that the image can actually run properly when deployed.
2019-07-24	feat(build): Configure Nixery image builder to set up env correctly	Vincent Ambo	1	-3/+27
	When running Nix inside of a container image, there are several environment-specific details that need to be configured appropriately. Most importantly, since one of the recent Nix 2.x releases, sandboxing during builds is enabled by default. This, however, requires kernel privileges which commonly aren't available to containers. Nixery's demo instance (for instance, hehe) is deployed on AppEngine where this type of container configuration is difficult, hence this change. Specifically the following were changed: * additional tools (such as tar/gzip) were introduced into the image because the builtins-toolset in Nix does not reference these tools via their store paths, which leads to them not being included automatically * Nix sandboxing was disabled in the container image * the users/groups required by Nix were added to the container setup. Note that these are being configured manually instead of via the tools from the 'shadow'-package, because the latter requires some user information (such as root) to be present already, which is not the case inside of the container
2019-07-23	chore: Add license scaffolding & contribution guidelines	Vincent Ambo	1	-0/+13

2019-07-23	feat(build): Add wrapper script & container image setup	Vincent Ambo	1	-1/+26
	Introduces a wrapper script which automatically sets the paths to the required runtime data dependencies. Additionally configures a container image derivation which will output a derivation with Nixery, Nix and other dependencies.
2019-07-23	feat(build): Introduce build configuration using Nix	Vincent Ambo	1	-0/+43
	Rather than migrating to Bazel, it seems more appropriate to use Nix for this project. The project is split into several different components (for data dependencies and binaries). A derivation for building an image for Nixery itself will be added.