This setup is greatly inspired by the one used for [0], although with notable modifications, such as: - a SASS preprocessor and CSS compressor - more streamlined NixOS integration tests - cleaned up service configuration - a few notes on how to do things better in the future [0]: https://github.com/Nix-Security-WG/nix-security-tracker/ Apart from cloning the Nix setup, there were additional steps: - Create an empty `src` directory, since the package requires it - In the development shell, run `django-admin startproject panel src` Note that while you can already do ```bash manage migrate manage runserver ``` the NixOS integration tests will fail, since `settings.py` needs careful massaging to expose knobs that can be turned from our systemd wrapper. The required changes are introduced in the next commit to make them observable. Noteworthy related work: - https://github.com/sephii/django.nix Rather mature setup with a clean interface, uses Caddy as reverse proxy. - https://git.dgnum.eu/mdebray/djangonix A work-in-progress attempt to capture more moving parts through the module system, in particular secrets. - https://github.com/DavHau/django-nixos Out of date and somewhat simplistic, but serves as a reasonable example for what can be done I chose the variant I'm intimately familiar with in order to be able to pass on knowledge or help with maintenance. But for the future I strongly recommend picking the good bits from the other implementations that control complexity in static configuration parts through Nix expressions. |
||
---|---|---|
.forgejo/workflows | ||
deployment | ||
infra | ||
keys | ||
matrix | ||
npins | ||
panel | ||
secrets | ||
services | ||
website | ||
.gitignore | ||
flake.lock | ||
flake.nix | ||
LICENSE | ||
README.md |
The Fediversity project
This repository contains all the code and code-related files having to do with the Fediversity project, with the notable exception of NixOps4 that is hosted on GitHub.
Content of this repository
Most of the directories in this repository have their own README going into more details as to what they are for. As an overview:
-
deployment/
contains bits and pieces having to do with auto-deployment of test VMs on a private Proxmox. -
infra/
contains the configurations for the various VMs that are in production for the project, for instance the Git instances or the Wiki. -
keys/
contains the public keys of the contributors to this project as well as the systems that we administrate. -
matrix/
contains everything having to do with setting up a fully-featured Matrix server. -
secrets/
contains the secrets that need to get injected into machine configurations. -
services/
contains our effort to make Fediverse applications work seemlessly together in our specific setting. -
website/
contains the framework and the content of the Fediversity website