From 5d9b32977ddd332f47f89aa30202b80906d3e719 Mon Sep 17 00:00:00 2001
From: Vincent Ambo <tazjin@google.com>
Date: Tue, 23 Jul 2019 21:48:27 +0100
Subject: feat(build): Introduce build configuration using Nix

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.
---
 tools/nixery/default.nix       |  43 ++++++++++++++++
 tools/nixery/go-deps.nix       | 111 +++++++++++++++++++++++++++++++++++++++++
 tools/nixery/index.html        |  90 ---------------------------------
 tools/nixery/static/index.html |  90 +++++++++++++++++++++++++++++++++
 4 files changed, 244 insertions(+), 90 deletions(-)
 create mode 100644 tools/nixery/default.nix
 create mode 100644 tools/nixery/go-deps.nix
 delete mode 100644 tools/nixery/index.html
 create mode 100644 tools/nixery/static/index.html

(limited to 'tools/nixery')

diff --git a/tools/nixery/default.nix b/tools/nixery/default.nix
new file mode 100644
index 000000000000..19e7df963a50
--- /dev/null
+++ b/tools/nixery/default.nix
@@ -0,0 +1,43 @@
+{ pkgs ? import <nixpkgs> {} }:
+
+with pkgs;
+
+rec {
+  # Go implementation of the Nixery server which implements the
+  # container registry interface.
+  #
+  # Users will usually not want to use this directly, instead see the
+  # 'nixery' derivation below, which automatically includes runtime
+  # data dependencies.
+  nixery-server = buildGoPackage {
+    name = "nixery-server";
+
+    # Technically people should not be building Nixery through 'go get'
+    # or similar (as other required files will not be included), but
+    # buildGoPackage requires a package path.
+    goPackagePath = "github.com/google/nixery";
+
+    goDeps = ./go-deps.nix;
+    src    = ./.;
+
+    meta = {
+      description = "Container image build serving Nix-backed images";
+      homepage    = "https://github.com/google/nixery";
+      license     = lib.licenses.ascl20;
+      maintainers = [ lib.maintainers.tazjin ];
+    };
+  };
+
+  # Nix expression (unimported!) which is used by Nixery to build
+  # container images.
+  nixery-builder = runCommand "build-registry-image.nix" {} ''
+    cat ${./build-registry-image.nix} > $out
+  '';
+
+  # Static files to serve on the Nixery index. This is used primarily
+  # for the demo instance running at nixery.appspot.com and provides
+  # some background information for what Nixery is.
+  nixery-static = runCommand "nixery-static" {} ''
+    cp -r ${./static} $out
+  '';
+}
diff --git a/tools/nixery/go-deps.nix b/tools/nixery/go-deps.nix
new file mode 100644
index 000000000000..57d9ecd64931
--- /dev/null
+++ b/tools/nixery/go-deps.nix
@@ -0,0 +1,111 @@
+# This file was generated by https://github.com/kamilchm/go2nix v1.3.0
+[
+  {
+    goPackagePath = "cloud.google.com/go";
+    fetch = {
+      type = "git";
+      url = "https://code.googlesource.com/gocloud";
+      rev = "edd0968ab5054ee810843a77774d81069989494b";
+      sha256 = "1mh8i72h6a1z9lp4cy9bwa2j87bm905zcsvmqwskdqi8z58cif4a";
+    };
+  }
+  {
+    goPackagePath = "github.com/golang/protobuf";
+    fetch = {
+      type = "git";
+      url = "https://github.com/golang/protobuf";
+      rev = "6c65a5562fc06764971b7c5d05c76c75e84bdbf7";
+      sha256 = "1k1wb4zr0qbwgpvz9q5ws9zhlal8hq7dmq62pwxxriksayl6hzym";
+    };
+  }
+  {
+    goPackagePath = "github.com/googleapis/gax-go";
+    fetch = {
+      type = "git";
+      url = "https://github.com/googleapis/gax-go";
+      rev = "bd5b16380fd03dc758d11cef74ba2e3bc8b0e8c2";
+      sha256 = "1lxawwngv6miaqd25s3ba0didfzylbwisd2nz7r4gmbmin6jsjrx";
+    };
+  }
+  {
+    goPackagePath = "github.com/hashicorp/golang-lru";
+    fetch = {
+      type = "git";
+      url = "https://github.com/hashicorp/golang-lru";
+      rev = "59383c442f7d7b190497e9bb8fc17a48d06cd03f";
+      sha256 = "0yzwl592aa32vfy73pl7wdc21855w17zssrp85ckw2nisky8rg9c";
+    };
+  }
+  {
+    goPackagePath = "go.opencensus.io";
+    fetch = {
+      type = "git";
+      url = "https://github.com/census-instrumentation/opencensus-go";
+      rev = "b4a14686f0a98096416fe1b4cb848e384fb2b22b";
+      sha256 = "1aidyp301v5ngwsnnc8v1s09vvbsnch1jc4vd615f7qv77r9s7dn";
+    };
+  }
+  {
+    goPackagePath = "golang.org/x/net";
+    fetch = {
+      type = "git";
+      url = "https://go.googlesource.com/net";
+      rev = "da137c7871d730100384dbcf36e6f8fa493aef5b";
+      sha256 = "1qsiyr3irmb6ii06hivm9p2c7wqyxczms1a9v1ss5698yjr3fg47";
+    };
+  }
+  {
+    goPackagePath = "golang.org/x/oauth2";
+    fetch = {
+      type = "git";
+      url = "https://go.googlesource.com/oauth2";
+      rev = "0f29369cfe4552d0e4bcddc57cc75f4d7e672a33";
+      sha256 = "06jwpvx0x2gjn2y959drbcir5kd7vg87k0r1216abk6rrdzzrzi2";
+    };
+  }
+  {
+    goPackagePath = "golang.org/x/sys";
+    fetch = {
+      type = "git";
+      url = "https://go.googlesource.com/sys";
+      rev = "fae7ac547cb717d141c433a2a173315e216b64c4";
+      sha256 = "11pl0dycm5d8ar7g1l1w5q2cx0lms8i15n8mxhilhkdd2xpmh8f0";
+    };
+  }
+  {
+    goPackagePath = "golang.org/x/text";
+    fetch = {
+      type = "git";
+      url = "https://go.googlesource.com/text";
+      rev = "342b2e1fbaa52c93f31447ad2c6abc048c63e475";
+      sha256 = "0flv9idw0jm5nm8lx25xqanbkqgfiym6619w575p7nrdh0riqwqh";
+    };
+  }
+  {
+    goPackagePath = "google.golang.org/api";
+    fetch = {
+      type = "git";
+      url = "https://code.googlesource.com/google-api-go-client";
+      rev = "069bea57b1be6ad0671a49ea7a1128025a22b73f";
+      sha256 = "19q2b610lkf3z3y9hn6rf11dd78xr9q4340mdyri7kbijlj2r44q";
+    };
+  }
+  {
+    goPackagePath = "google.golang.org/genproto";
+    fetch = {
+      type = "git";
+      url = "https://github.com/google/go-genproto";
+      rev = "c506a9f9061087022822e8da603a52fc387115a8";
+      sha256 = "03hh80aqi58dqi5ykj4shk3chwkzrgq2f3k6qs5qhgvmcy79y2py";
+    };
+  }
+  {
+    goPackagePath = "google.golang.org/grpc";
+    fetch = {
+      type = "git";
+      url = "https://github.com/grpc/grpc-go";
+      rev = "977142214c45640483838b8672a43c46f89f90cb";
+      sha256 = "05wig23l2sil3bfdv19gq62sya7hsabqj9l8pzr1sm57qsvj218d";
+    };
+  }
+]
diff --git a/tools/nixery/index.html b/tools/nixery/index.html
deleted file mode 100644
index ebec9968c0c9..000000000000
--- a/tools/nixery/index.html
+++ /dev/null
@@ -1,90 +0,0 @@
-<!DOCTYPE html>
-<html>
-  <head>
-    <meta charset="utf-8">
-    <meta name="viewport" content="width=device-width, initial-scale=1">
-    <title>Nixery</title>
-    <style>
-      body {
-        margin: 40px auto;
-        max-width: 650px;
-        line-height: 1.6;
-        font-size: 18px;
-        color: #444;
-        padding: 010px
-      }
-
-      h1, h2, h3 {
-        line-height: 1.2
-      }
-    </style>
-  </head>
-  <body>
-    <header>
-      <h1>Nixery</h1>
-      <aside>ad-hoc container images - powered by <a href="https://nixos.org/nix/">Nix</a></aside>
-    </header>
-    <h3>What is this?</h3>
-    <p>
-      Nixery provides the ability to pull ad-hoc container images from a Docker-compatible registry
-      server. The image names specify the contents the image should contain, which are then
-      retrieved and built by the Nix package manager.
-    </p>
-    <p>
-      Nix is also responsible for the creation of the container images themselves. To do this it
-      uses an interesting layering strategy described in
-      <a href="https://grahamc.com/blog/nix-and-layered-docker-images">this blog post</a>.
-    </p>
-    <h3>How does it work?</h3>
-    <p>
-      Simply point your local Docker installation (or other compatible registry client) at Nixery
-      and ask for an image with the contents you desire. Image contents are path separated in the
-      name, so for example if you needed an image that contains a shell and <code>emacs</code> you
-      could pull it as such:
-    </p>
-    <p>
-      <code>nixery.appspot.com/shell/emacs25-nox</code>
-    </p>
-    <p>
-      Image tags are currently <i>ignored</i>. Every package name needs to correspond to a key in the
-      <a href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/all-packages.nix">nixpkgs package set</a>.
-    </p>
-    <p>
-      There are some special <i>meta-packages</i> which you <strong>must</strong> specify as the
-      first package in an image. These are:
-    </p>
-    <ul>
-      <li><code>shell</code>: Provides default packages you would expect in an interactive environment</li>
-      <li><code>builder</code>: Provides the above as well as Nix's standard build environment</li>
-    </ul>
-    <p>
-      Hence if you needed an interactive image with, for example, <code>htop</code> installed you
-      could run <code>docker run -ti nixery.appspot.com/shell/htop bash</code>.
-    </p>
-    <h3>FAQ</h3>
-    <p>
-      Technically speaking none of these are frequently-asked questions (because no questions have
-      been asked so far), but I'm going to take a guess at a few anyways:
-    </p>
-    <ul>
-      <li>
-        <strong>Where is the source code for this?</strong>
-        <br>
-        Not yet public, sorry. Check back later(tm).
-      </li>
-      <li>
-        <strong>Which revision of <code>nixpkgs</code> is used?</strong>
-        <br>
-        Currently whatever was <code>HEAD</code> at the time I deployed this. One idea I've had is
-        to let users specify tags on images that correspond to commits in nixpkgs, however there is
-        some potential for abuse there (e.g. by triggering lots of builds on commits that have
-        broken Hydra builds) and I don't want to deal with that yet.
-      </li>
-      <li>
-        <strong>Who made this?</strong>
-        <br>
-        <a href="https://twitter.com/tazjin">@tazjin</a>
-      </li>
-    </ul>
-  </body>
-</html>
diff --git a/tools/nixery/static/index.html b/tools/nixery/static/index.html
new file mode 100644
index 000000000000..ebec9968c0c9
--- /dev/null
+++ b/tools/nixery/static/index.html
@@ -0,0 +1,90 @@
+<!DOCTYPE html>
+<html>
+  <head>
+    <meta charset="utf-8">
+    <meta name="viewport" content="width=device-width, initial-scale=1">
+    <title>Nixery</title>
+    <style>
+      body {
+        margin: 40px auto;
+        max-width: 650px;
+        line-height: 1.6;
+        font-size: 18px;
+        color: #444;
+        padding: 010px
+      }
+
+      h1, h2, h3 {
+        line-height: 1.2
+      }
+    </style>
+  </head>
+  <body>
+    <header>
+      <h1>Nixery</h1>
+      <aside>ad-hoc container images - powered by <a href="https://nixos.org/nix/">Nix</a></aside>
+    </header>
+    <h3>What is this?</h3>
+    <p>
+      Nixery provides the ability to pull ad-hoc container images from a Docker-compatible registry
+      server. The image names specify the contents the image should contain, which are then
+      retrieved and built by the Nix package manager.
+    </p>
+    <p>
+      Nix is also responsible for the creation of the container images themselves. To do this it
+      uses an interesting layering strategy described in
+      <a href="https://grahamc.com/blog/nix-and-layered-docker-images">this blog post</a>.
+    </p>
+    <h3>How does it work?</h3>
+    <p>
+      Simply point your local Docker installation (or other compatible registry client) at Nixery
+      and ask for an image with the contents you desire. Image contents are path separated in the
+      name, so for example if you needed an image that contains a shell and <code>emacs</code> you
+      could pull it as such:
+    </p>
+    <p>
+      <code>nixery.appspot.com/shell/emacs25-nox</code>
+    </p>
+    <p>
+      Image tags are currently <i>ignored</i>. Every package name needs to correspond to a key in the
+      <a href="https://github.com/NixOS/nixpkgs/blob/master/pkgs/top-level/all-packages.nix">nixpkgs package set</a>.
+    </p>
+    <p>
+      There are some special <i>meta-packages</i> which you <strong>must</strong> specify as the
+      first package in an image. These are:
+    </p>
+    <ul>
+      <li><code>shell</code>: Provides default packages you would expect in an interactive environment</li>
+      <li><code>builder</code>: Provides the above as well as Nix's standard build environment</li>
+    </ul>
+    <p>
+      Hence if you needed an interactive image with, for example, <code>htop</code> installed you
+      could run <code>docker run -ti nixery.appspot.com/shell/htop bash</code>.
+    </p>
+    <h3>FAQ</h3>
+    <p>
+      Technically speaking none of these are frequently-asked questions (because no questions have
+      been asked so far), but I'm going to take a guess at a few anyways:
+    </p>
+    <ul>
+      <li>
+        <strong>Where is the source code for this?</strong>
+        <br>
+        Not yet public, sorry. Check back later(tm).
+      </li>
+      <li>
+        <strong>Which revision of <code>nixpkgs</code> is used?</strong>
+        <br>
+        Currently whatever was <code>HEAD</code> at the time I deployed this. One idea I've had is
+        to let users specify tags on images that correspond to commits in nixpkgs, however there is
+        some potential for abuse there (e.g. by triggering lots of builds on commits that have
+        broken Hydra builds) and I don't want to deal with that yet.
+      </li>
+      <li>
+        <strong>Who made this?</strong>
+        <br>
+        <a href="https://twitter.com/tazjin">@tazjin</a>
+      </li>
+    </ul>
+  </body>
+</html>
-- 
cgit 1.4.1