No description
a73ca3f43d
This uses the actual Bazel build, using a variety of tricks and hacks to make it actually work. Bazel really wants to download linux binaries from the internet and run them. In lieu of trying to fix the build system to not do this, we instead put bazel inside an FHS environment, which allows the binaries to find their dependencies. We also have to patch a few things: * We use build --nobuild instead of fetch, so we only fetch the dependencies we actually need for the build and not, say, Windows binaries. * We don't remove rules_cc, because we need it as an external dependency, not bundled. * We do some manual fixes on the cache before packing, because we need to remove some in-tree sources (so they don't cause the hash to break, since the hashes differ each time they're generated), and also remove some extraneous files. * We explicitly turn off the repository and disk caches, because the .bazelrc at the root of the Gerrit tree turns them on, with paths pointing into the user's home directory. * detzip is used instead of the zip binary for packing bower_components into an archive. detzip doesn't create entries for directories, and also doesn't store most metadata (timestamps, etc.), and uses store (i.e. uncompressed) compression only. It also sorts the file tree before writing them into the file. Change-Id: I572c43f7175067ecb1b85cdf40dda13a52de1439 Reviewed-on: https://cl.tvl.fyi/c/depot/+/252 Reviewed-by: tazjin <mail@tazj.in> |
||
---|---|---|
bin | ||
docs | ||
fun | ||
lisp/dns | ||
net | ||
nix | ||
ops | ||
overrides | ||
presentations | ||
third_party | ||
tools | ||
users | ||
web | ||
.envrc | ||
.git-blame-ignore-revs | ||
.gitignore | ||
.rgignore | ||
ci-builds.nix | ||
default.nix | ||
LICENSE | ||
OWNERS | ||
README.md |
depot
This repository is the monorepo for the community around tazjin's virus lounge, containing our personal tools and infrastructure. Everything in here is built using Nix.
If you've ended up here and have no idea who I am, feel free to follow me on Twitter.
Highlights
Tools
tools/emacs
contains my personal Emacs configuration (packages & config)fun/aoc2019
contains solutions for a handful of Advent of Code 2019 challenges, before I ran out of interesttools/blog_cli
contains my tool for writing new blog posts and storing them in the DNS zonetools/cheddar
contains a source code and Markdown rendering tool that is integrated with my cgit instance to render files in various viewsops/kms_pass.nix
is a tiny tool that emulates the user-interface ofpass
, but actually uses Google Cloud KMS for secret decryptionops/kontemplate
contains my Kubernetes resource templating tool (with which the services in this repository are deployed!)ops/besadii
contains a tool that runs as the gitpost-receive
-hook on my git server to trigger builds on sourcehut.third_party/nix
contains my fork of the Nix package manager
Packages / Libraries
nix/buildGo
implements a Nix library that can build Go software in the style of Bazel'srules_go
. Go programs in this repository are built using this library.nix/buildLisp
implements a Nix library that can build Common Lisp software. Currently only SBCL is supported. Lisp programs in this repository are built using this library.tools/emacs-pkgs
contains various Emacs libraries that my Emacs setup uses, for example:dottime.el
provides dottime in the Emacs modelinenix-util.el
provides editing utilities for Nix filesterm-switcher.el
is an ivy-function for switching between vterm buffers
net/alcoholic_jwt
contains an easy-to-use JWT-validation library for Rustnet/crimp
contains a high-level HTTP client using cURL for Rust
Services
Services in this repository are deployed on a Google Kubernetes Engine cluster using Nixery.
web/blog
andweb/homepage
contain my blog and website setup (serving at tazj.in)web/cgit-taz
contains a slightly patched version ofcgit
that serves my git web interface at git.tazj.inops/journaldriver
contains a small Rust daemon that can forward logs from journald to Stackdriver Logging
Miscellaneous
Presentations I've given in the past are in the presentations
folder, these
cover a variety of topics and some of them have links to recordings.
There's a few fun things in the fun/
folder, often with context given in the
README. Check out my list of the best tools for example.
Contributing
If you'd like to contribute to any of the tools in here, please check out the contribution guidelines.