mdebray/tvl-depot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
1372 commits 5 branches 0 tags 172 MiB
CSS 33%
Nix 26.8%
Rust 19.3%
Haskell 5.8%
Emacs Lisp 4.5%
Other 10.1%
Find a file
Vincent Ambo db30770101 fix(kontemplate): Make build compatible with readTree 
The kontemplate build will keep using `buildGoPackage` for now until
I've had the time to add tests to //nix/buildGo
2019-12-20 22:19:52 +00:00
bin fix: Various minor fixes for new repository layout 2019-12-20 20:44:00 +00:00
docs chore(kontemplate): Prepare kontemplate for depot-merge 2019-12-20 22:13:07 +00:00
fun style(fun/logo): Use a much lighter colour for the logo quote 2019-12-20 21:34:18 +00:00
nix chore(yants): Move tests into subfolder & add to CI builds 2019-12-20 21:53:19 +00:00
ops fix(kontemplate): Make build compatible with readTree 2019-12-20 22:19:52 +00:00
overrides fix(kontemplate): Make build compatible with readTree 2019-12-20 22:19:52 +00:00
third_party fix(kontemplate): Make build compatible with readTree 2019-12-20 22:19:52 +00:00
tools chore: Significantly restructure folder layout 2019-12-20 20:18:41 +00:00
web style(cgit-taz): Embed repository logo 2019-12-20 21:18:53 +00:00
.envrc feat(overrides/kontemplate): Automatically use primary-cluster.yaml 2019-12-20 20:55:25 +00:00
.gitignore chore(kontemplate): Prepare kontemplate for depot-merge 2019-12-20 22:13:07 +00:00
.travis.yml chore(kontemplate): Prepare kontemplate for depot-merge 2019-12-20 22:13:07 +00:00
ci-builds.nix fix(kontemplate): Make build compatible with readTree 2019-12-20 22:19:52 +00:00
default.nix chore(kontemplate): Prepare kontemplate for depot-merge 2019-12-20 22:13:07 +00:00
LICENSE chore(kontemplate): Prepare kontemplate for depot-merge 2019-12-20 22:13:07 +00:00
read-tree.nix fix: Various minor fixes for new repository layout 2019-12-20 20:44:00 +00:00
README.md chore(kontemplate): Prepare kontemplate for depot-merge 2019-12-20 22:13:07 +00:00

README.md

depot

Build Status

This repository is the monorepo for my personal tools and infrastructure. Everything in here is built using Nix with an automatic attribute-set layout that mirrors the filesystem layout of the repository (this might feel familiar to users of Bazel).

This repository used to be hosted on GitHub, but for a variety of reasons I have decided to take over the management of personal infrastructure - of which this repository is a core component.

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 interest
  • tools/blog_cli contains my tool for writing new blog posts and storing them in the DNS zone
  • ops/kms_pass.nix is a tiny tool that emulates the user-interface of pass, but actually uses Google Cloud KMS for secret decryption

Packages / Libraries

  • nix/buildGo implements a Nix library that can build Go software in the style of Bazel's rules_go. Go 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][https://dotti.me] in the Emacs modeline
    • nix-util.el provides editing utilities for Nix files
    • term-switcher.el is an ivy-function for switching between vterm buffers

Services

Services in this repository are deployed on a Google Kubernetes Engine cluster using Nixery.

  • web/tazblog contains my blog software (serving at tazj.in)
  • web/cgit-taz contains a slightly patched version of cgit that serves my git web interface at git.tazj.in
  • ops/sync-gcsr contains a tiny service that synchronises a Google Cloud Source Repository with a local disk path. My cgit setup uses this under-the-hood.
  • fun/gemma contains a no-longer-maintained service that served as an experiment in "household task management" - it's kept in here because I find it interesting

Contributing

If you'd like to contribute to any of the tools in here, please check out the contribution guidelines.