From 6716bf018c465f4b943eef0e6716caa7a54940da Mon Sep 17 00:00:00 2001 From: Vincent Ambo Date: Wed, 20 Apr 2022 16:41:20 +0200 Subject: chore(nixery): Housekeeping for depot compatibility Cleans up a whole bunch of things I wanted to get out of the door right away: * depot internal references to //third_party/nixery have been replaced with //tools/nixery * cleaned up files from Github * fixed SPDX & Copyright headers * code formatting and inclusion in //tools/depotfmt checks Change-Id: Iea79f0fdf3aa04f71741d4f4032f88605ae415bb Reviewed-on: https://cl.tvl.fyi/c/depot/+/5486 Tested-by: BuildkiteCI Reviewed-by: tazjin Autosubmit: tazjin --- tools/nixery/docs/src/nixery.md | 6 +----- tools/nixery/docs/src/run-your-own.md | 17 ++++++++++------- 2 files changed, 11 insertions(+), 12 deletions(-) (limited to 'tools/nixery/docs/src') diff --git a/tools/nixery/docs/src/nixery.md b/tools/nixery/docs/src/nixery.md index 7b78ddf5aaf8..d9ba179010f6 100644 --- a/tools/nixery/docs/src/nixery.md +++ b/tools/nixery/docs/src/nixery.md @@ -68,10 +68,6 @@ production project we recommend setting up a private instance. The public Nixery at `nixery.dev` is run on a best-effort basis and we make no guarantees about availability. -### Is this an official Google project? - -**No.** Nixery is not officially supported by Google. - ### Who made this? Nixery was written by [tazjin][], but many people have contributed to Nix over @@ -81,4 +77,4 @@ time, maybe you could become one of them? [Nix]: https://nixos.org/nix [layering strategy]: https://storage.googleapis.com/nixdoc/nixery-layers.html [layers]: https://grahamc.com/blog/nix-and-layered-docker-images -[tazjin]: https://github.com/tazjin +[tazjin]: https://tazj.in diff --git a/tools/nixery/docs/src/run-your-own.md b/tools/nixery/docs/src/run-your-own.md index cf4dc2ce6166..7ed8bdd0bc0a 100644 --- a/tools/nixery/docs/src/run-your-own.md +++ b/tools/nixery/docs/src/run-your-own.md @@ -65,13 +65,17 @@ use it with your own packages. There are three options available: ### 2.1. With a container image -The easiest way to run Nixery is to build a container image. -This section assumes that the container runtime used is Docker, -please modify instructions accordingly if -you are using something else. +The easiest way to run Nixery is to build a container image. This +section assumes that the container runtime used is Docker, please +modify instructions accordingly if you are using something else. -With a working Nix installation, building Nixery is done by invoking `nix-build --A nixery-image` from a checkout of the [Nixery repository][repo]. +With a working Nix installation, you can clone and build the Nixery +image like this: + +``` +git clone https://code.tvl.fyi/depot.git:/tools/nixery.git +nix-build -A nixery-image +``` This will create a `result`-symlink which points to a tarball containing the image. In Docker, this tarball can be loaded by using `docker load -i result`. @@ -184,7 +188,6 @@ If the directory doesn't exist, Nixery will run fine but serve 404. [nixery#4]: https://github.com/tazjin/nixery/issues/4 [Nix]: https://nixos.org/nix [gcs]: https://cloud.google.com/storage/ -[repo]: https://github.com/tazjin/nixery [signed-urls]: under-the-hood.html#5-image-layers-are-requested [ADC]: https://cloud.google.com/docs/authentication/production#finding_credentials_automatically [nixinstall]: https://nixos.org/manual/nix/stable/installation/installing-binary.html -- cgit 1.4.1