How bearstech/acme works
Main Components
a) Core Components:
• ACME Client Engine (acme.sh main script)
• Certificate Management System
• DNS API Integration Layer
• Deployment System
• Notification System
b) External Interfaces:
• Certificate Authorities (ZeroSSL, Let's Encrypt, etc.)
• DNS Providers
• Web Servers (Apache, Nginx, etc.)
• Notification Services
┌─────────────────────────────────────────────────────────────┐
• Client Interface │
• (Command Line Interface / Docker Container Interface) │
• ┤
• Core Services │
• ┬──────────────┬──────────────┬──────────────┤
• Certificate │ ACME │ DNS │ Deployment │
• Management │ Protocol │ API │ System │
• System │ Client │ Interface │ │
• ┴──────────────┴──────────────┴──────────────┤
• Integration Layer │
• ┬──────────────┬──────────────┬──────────────┤
• Web Server │ DNS │ Notification │ Storage │
• Integrations│ Providers │ Services │ System │
• ┴──────────────┴──────────────┴──────────────┘
Component Details
a) Certificate Management System:
• Issue certificates
• Renew certificates
• Revoke certificates
• Key management
• Certificate storage
b) DNS API Interface:
• To 100+ DNS providers
• DNS record management
• DNS verification
c) Deployment System:
• Apache deployment
• Nginx deployment
• Custom server deployment
• Automatic reload handlers
d) Notification System:
• Email notifications
• Messaging services
• Custom notification hooks
Data Flow Indicators
• Certificate request flow
• DNS verification flow
• Deployment process flow
• Notification triggers
Integration Points
Connections to:
• Multiple CA servers
• DNS provider APIs
• Web server configurations
• Storage systems