Examples of piler configurations

Piler enterprise 2.2 deployments

• Single node: every component on one host, no-tenant or multi-tenant, depending on the license
• Multi-node, multi-tenant: a master and several workers on separate hosts, emails in S3-compatible storage, for hosting providers and MSPs

Scripts

• piler-upgrade.sh: upgrades an installation of the 2.2 Docker examples (a single node, or a node of a multi-node deployment): shows the upgrade notes, backs up the database, and waits until the new containers are healthy
• piler-backup.sh: daily backups of an installation of the 2.2 Docker examples into a restic repository (S3, SFTP, a directory), and the restore on a new host

Monitoring

• Monitoring: piler-ui's metrics, alert rules (Prometheus format, with tests), and a Grafana Cloud setup with Alloy and a dashboard

Hosting

• Purging a tenant: delete a tenant's database, index, stored emails and settings on every node, with safety checks

Mail flow, TLS, security

• Postfix as MX: receive the journal emails and pass them to piler
• Let's Encrypt with Traefik: an A-grade TLS setup
• OWASP ModSecurity WAF in front of piler

Backup

• Raw data to an S3 bucket
• Daily export to an S3 bucket

Older versions

The examples of piler 2.0 and 2.1, and the first Docker setups, are in archive. Use the 2.2 examples for new deployments.