Deuxfleurs/nixcfg
17
6
Fork 2
Code Issues 15 Pull requests 2 Projects Releases Wiki Activity
Nix system configuration for Deuxfleurs clusters
411 commits 12 branches 0 tags 2 MiB
HCL 38.2%
JavaScript 29.2%
Nix 16.2%
Shell 4.9%
Smarty 3.9%
Other 7.6%
Find a file
Alex Auvolat a0db30ca26 Sanitize DNS configuration 
- get rid of outside nameserver, unbound does the recursive resolving
  itself (and it checks DNSSEC)
- remove CAP_NET_BIND_SERVICE for Consul as it is no longer binding on
  port 53 (was already obsolete)
- make unbound config independant of LAN IPv4 address
2023-03-24 12:58:44 +01:00
cluster Sanitize DNS configuration 2023-03-24 12:58:44 +01:00
doc wgautomesh actually on prod 2023-03-24 12:01:38 +01:00
experimental staging: deploy things on bespin 2023-01-04 10:06:06 +01:00
nix Sanitize DNS configuration 2023-03-24 12:58:44 +01:00
.gitignore Modularize and prepare to support multiple clusters 2022-02-09 12:09:49 +01:00
deploy_nixos wgautomesh actually on prod 2023-03-24 12:01:38 +01:00
deploy_passwords cleanup 2022-12-23 00:07:02 +01:00
deploy_pki added scorpio site and abricot node 2023-03-15 17:10:38 +01:00
gen_pki Fix access to consul for non-server nodes 2022-08-24 16:58:50 +02:00
passwd edited passwd command to set bash as interpreter 2022-11-09 19:02:02 +01:00
README.md reorganize some things 2022-12-24 22:59:37 +01:00
restic_summary cleanup 2022-12-23 00:07:02 +01:00
secretmgr Improve secretmgr more, update secrets for staging 2022-12-25 22:12:38 +01:00
sshtool fix cleanup of deploypass 2023-03-15 17:49:31 +01:00
tlsproxy Remove hardcoded years in deuxfleurs.nix 2023-01-01 19:43:35 +01:00
upgrade_nixos upgrade nixos 2023-03-15 17:50:06 +01:00

README.md

Deuxfleurs on NixOS!

This repository contains code to run Deuxfleur's infrastructure on NixOS.

Our abstraction stack

We try to build a generic abstraction stack between our different resources (CPU, RAM, disk, etc.) and our services (Chat, Storage, etc.), we develop our own tools when needed.

Our first abstraction level is the NixOS level, which installs a bunch of standard components:

  • Wireguard: provides encrypted communication between remote nodes
  • Nomad: schedule containers and handle their lifecycle
  • Consul: distributed key value store + lock + service discovery
  • Docker: package, distribute and isolate applications

Then, inside our Nomad+Consul orchestrator, we deploy a number of base services:

  • Garage: S3-compatible lightweight object store for self-hosted geo-distributed deployments (we also have a legacy glusterfs cluster)
  • DiploNAT: network automation (firewalling, upnp igd)
  • Bottin: authentication and authorization (LDAP protocol, consul backend)
  • Guichet: a dashboard for our users and administrators
  • Stolon + PostgreSQL: distributed relational database
  • Prometheus + Grafana: monitoring

Some services we provide based on this abstraction:

  • Websites: Garage (static) + fediverse blog (Plume)
  • Chat: Synapse + Element Web (Matrix protocol)
  • Email: Postfix SMTP + Dovecot IMAP + opendkim DKIM + Sogo webmail | Alps webmail (experimental)
  • Visioconference: Jitsi
  • Collaboration: CryptPad

As a generic abstraction is provided, deploying new services should be easy.

How to use this?

See the following documentation topics: