| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Add a Makefile to build the local binaries. Rename all the commands
without a dash.
We can build the commands with `make all` or by being explicit, for
example `make bin/x509-info`.
Add a common package to keep track of build information (commit and
build date) so we can reuse the same pattern across all the commands.
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm not using it as a desktop, and the current router is getting old and
will likely fail in the near future. It's also a debian machine
configured manually, so let's reconfigure carmel as our new router.
There are three NICs in the host: 2 are 10Gb and one is 1Gb. The 1Gb
will be used as the upstream interface, and one of the 10Gb will be for
the LAN.
There are 2 VLANs to configure: one for IoT devices and one for guest.
|
|
|
|
| |
Change-Id: I0235d851df781430abe87d503c652bd97b6e1f1a
|
|
|
|
|
|
|
|
|
| |
And configure them to run nixpkgs-fmt and shellcheck.
Change-Id: I0aa2025e368b80c5e7d90a4dc05448494525e31e
Reviewed-on: https://cl.fcuny.net/c/world/+/590
Reviewed-by: Franck Cuny <franck@fcuny.net>
Tested-by: CI
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a patchset is created, gerrit will call this tool with a number of
arguments.
This hook triggers a build with buildKite for the given patchset, and
add a comment to gerrit with a link to the build.
We do not wait for the build to be successful to update gerrit. This
will be done by another hook which the buildKite agents will call once
they are done with the build.
Change-Id: Iaa221765f3c52875ec37c5d282ba0557291eb5a4
Reviewed-on: https://cl.fcuny.net/c/world/+/171
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
|
|
|
|
|
|
| |
There's no need to have a flake.nix for the notes, we can use the same
mechanism as for the blog and resume.
Add a README so I remember how to use this in the future.
|
|
|
|
|
|
| |
There's no need to have multiple `flake.nix` in the repository. Make the
blog part of the flake configuration at the root level of the
repository, delete the one in the blog, and update the documentation.
|
| |
|
|
|
|
|
| |
In a monorepo setup, the CI configuration is not used at this level of
the tree, and the gitignore/envrc are not relevant.
|
|
In a monorepo setup, the CI configuration is not used at this level of
the tree, and the gitignore/envrc are not relevant.
|