@ -0,0 +1,7 @@
* Creating CI jobs
The kookienomicon uses a self-hosted drone CI to run jobs for all
projects in the repository that have the required configuration
Shared configuration is kept in =/ci=.
@ -0,0 +1,34 @@
This repository contains a wide variety of projects that I develop
in my free time, mostly for fun. This directory contains
documentation for many of these projects, as well as the monorepo
Furthermore I will keep track of TODO lists and incidence logs on my
infrastructure (that don't contain any sensitive information) in
this directory tree as well.
** Why a monorepo
I start a lot of projects in my free time. I'm prone to having
ideas and only seeing them through half way, or starting many small
projects that each don't take up _that_ much time to create, but
then get forgotten about and never maintained again.
Creating a repository, CI jobs, documentation, etc for each of
these small projects started taking up a lot of effort on my part,
so creating a monorepo, to keep them all in a single place, started
as an attepmt to de-duplicate work for myself.
At the same time I like the idea of having a shared history of my
work and a single repository I can clone (or point people to) to
get a good picture of the work that I do outside of my day-job or
software research work.
Following is a list of general pages.
- [[file:todo.org][Infrastructure TODOs]]
- [[file:ci.org][Creating CI jobs]]
@ -0,0 +1,23 @@
* Infrastructure TODO
Over the last few months I have let my personal infrastructure fall
into disarray. This is a list of things I need to investigate to
- [ ] Setup CI jobs for kookienomicon with [[https://drone.io][drone]]
- [ ] Unify nixpkgs tree between tempest and uwu
- [ ] Pin hyperion & gaia to nixpkgs-stable
- [ ] Failing systemd units
- [ ] nextcloud-update-plugins
- [ ] acme-kookiejar.tech
- [ ] acme-spacekookie.de
- [ ] acme-hyperion.kookie.space