Integrated Let's Encrypt certification for Elixir-powered sites without requiring external processes.
SiteEncrypt is an Elixir library that provides integrated TLS/SSL certification via Let's Encrypt for Elixir-based web applications. It eliminates the need for external processes like Certbot by allowing sites to automatically obtain and renew certificates directly within the Elixir runtime. The library is designed for small-to-medium Elixir sites that do not sit behind reverse proxies such as nginx.
Elixir developers building small-to-medium web applications, particularly those using the Phoenix framework, who want to handle TLS certification natively without relying on external tools or reverse proxies.
Developers choose SiteEncrypt for its seamless integration into the Elixir application lifecycle, reducing operational overhead by automating certificate management internally. Its unique selling point is the ability to use either a native Elixir ACME client (experimental) or the more stable Certbot client, offering flexibility while keeping the certification process within the Elixir ecosystem.
Integrated certification via Let's encrypt for Elixir-powered sites
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically obtains and renews Let's Encrypt certificates without external processes, as shown in the startup logs where it self-certifies upon first boot.
Uses a custom endpoint module that replaces `use Phoenix.Endpoint`, allowing straightforward setup within Phoenix applications without complex configuration.
Configures local, staging, and production modes via environment variables like CERT_MODE, enabling safe testing with Let's Encrypt's staging servers.
Generates temporary self-signed certificates during initial setup, ensuring the site remains accessible while waiting for proper certification, as mentioned in the logs.
The pure Elixir ACME client is labeled 'very new' and 'not considered stable' in the README, forcing reliance on Certbot for reliability, which adds external dependency.
The README explicitly warns that 'the API is not stable' and expects 'breaking changes in the future,' making it risky for long-term projects without frequent updates.
Requires careful management of environment variables like SITE_ENCRYPT_DB to avoid certificate loss during deployments, adding operational overhead compared to simpler solutions.