Explore >> Select a destination
|
You are here 
|
jnsgr.uk | ||
| | | | |
jmmv.dev
|
|
| | | | | From day one, the Kyua source tree has had docstring annotations for all of its symbols. The goal of such docstrings is to document the code for the developers of Kyua: these docstrings were never intended to turn into pre-generated HTML documentation because Kyua does not offer an API once installed. As you might have noticed, Doxygen is an optional component of the build and it used to run on each make invocation. This changed "recently". Nowadays, Doxygen is only run asynchronously on Travis CI to report docstring inconsistencies post-submission (see the DO=apidocs matrix entry if you are impatient). Combined with feature branches that are only merged into master when green, this is as good as the previous approach of running Doxygen along the build. Scratch that: this is even better because running Doxygen locally on each build took significant resources and penalized edit/build/test cycles. | |
| | | | |
kalbas.it
|
|
| | | | | We use Nix, a reproducible package manager, to provide a fixed environment with Hugo and the Hugo theme we want to use. This method does not require us to copy the theme into our repository or to add it as a submodule. | |
| | | | |
blog.thalheim.io
|
|
| | | | | No such file or directory: How I stopped worrying and started loving binaries on NixOS. In this article, I will discuss the technical issue of running pre-compiled executables on NixOS, and how we can improve the user experience by making these binaries work seamlessly using nix-ld. One of the key benefits of NixOS is its focus on purity and reproducibility. The operating system is designed to ensure that the system configuration and installed software are always in a known and predictable state. | |
| | | | |
www.koyeb.com
|
|
| | | We decided to build our own serverless engine, one that would not be limited by existing implementations. The first version of Koyeb was built on top of Kubernetes and allowed us to quickly build a working cloud platform. After a few months of operating with this version, we decided to move user workloads from Kubernetes to a custom stack based on Nomad, Firecracker, and Kuma. | ||
