Deployment
Best practices for deploying applications that use the Acme SDK.
Environment Setup
Production Checklist
Before deploying to production:
- Use production API keys (not sandbox)
- Set appropriate timeouts and retry limits
- Configure error monitoring
- Enable request logging
- Set up webhook endpoints
Environment Variables
Required environment variables:
# Required
ACME_API_KEY=sk_live_xxxxx
# Optional
ACME_API_VERSION=v3
ACME_TIMEOUT=30000
ACME_RETRIES=3
ACME_WEBHOOK_SECRET=whsec_xxxxx
Platform Guides
Node.js
// server.js
;
;
;
;
'/api/users/:id', ;
3000;
Serverless (AWS Lambda)
// handler.js
;
// Initialize outside handler for connection reuse
;
;
Edge Functions (Cloudflare Workers)
// worker.js
;
;
Monitoring
Health Checks
Implement health checks to monitor SDK connectivity:
'/health', ;
Error Tracking
Integrate with error tracking services:
;
;
;
Rate Limiting
The Acme API has rate limits. Handle them gracefully:
| Plan | Requests/min | Burst |
|---|---|---|
| Free | 60 | 10 |
| Pro | 600 | 100 |
| Enterprise | 6000 | 1000 |
;
try catch error
Security
API Key Rotation
Rotate API keys periodically:
- Generate a new key in the Dashboard
- Update your environment variables
- Deploy the update
- Revoke the old key
Webhook Security
Always verify webhook signatures:
;
if !isValid
Support
- Documentation: You're here!
- API Status: status.acme.dev
- Support: support@acme.dev
- Enterprise: enterprise@acme.dev