Reason: - do not slow down the garage web endpoint - required now that we map domain name to a garage bucket
Deuxfleurs on NixOS!
This repository contains code to run Deuxfleurs' 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:
- Data management
- Garage: S3-compatible lightweight object store for self-hosted geo-distributed deployments
- Stolon + PostgreSQL: distributed relational database
- Network Control Plane
- User Management
- 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)
- Aerogramme: an encrypted IMAP server
- 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:
- Quick start and onboarding for new administrators
- How to add new nodes to a cluster (rapid overview)
- Architecture of this repo, how the scripts work
- List of TCP and UDP ports used by services
- Why not Ansible?
Got personal services in addition to Deuxfleurs at home?
cluster/prod/register_external_services.sh. In bash, we register a redirect from Tricot to your own services or your personal reverse proxy.