documenso-deploy-integration
Deploy Documenso integrations across different platforms and environments. Use when deploying to cloud platforms, containerizing applications, or setting up infrastructure for Documenso integrations. Trigger with phrases like "deploy documenso", "documenso docker", "documenso kubernetes", "documenso cloud deployment".
Best use case
documenso-deploy-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Deploy Documenso integrations across different platforms and environments. Use when deploying to cloud platforms, containerizing applications, or setting up infrastructure for Documenso integrations. Trigger with phrases like "deploy documenso", "documenso docker", "documenso kubernetes", "documenso cloud deployment".
Teams using documenso-deploy-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/documenso-deploy-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How documenso-deploy-integration Compares
| Feature / Agent | documenso-deploy-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Deploy Documenso integrations across different platforms and environments. Use when deploying to cloud platforms, containerizing applications, or setting up infrastructure for Documenso integrations. Trigger with phrases like "deploy documenso", "documenso docker", "documenso kubernetes", "documenso cloud deployment".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Documenso Deploy Integration
## Overview
Deploy Documenso-integrated applications and self-hosted Documenso instances to Docker, Kubernetes, serverless, and cloud platforms. Covers both app deployment (your code that uses the Documenso API) and self-hosted Documenso deployment.
## Prerequisites
- Application ready for deployment
- Cloud platform account (AWS, GCP, Azure)
- Docker installed locally
- Completed `documenso-multi-env-setup`
## Instructions
### Step 1: Dockerize Your Documenso Integration
```dockerfile
# Dockerfile
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build
FROM node:20-alpine AS runtime
WORKDIR /app
RUN addgroup -S app && adduser -S app -G app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY --from=builder /app/package.json .
USER app
EXPOSE 3000
CMD ["node", "dist/server.js"]
# Note: DOCUMENSO_API_KEY injected at runtime, never baked into image
```
### Step 2: Self-Hosted Documenso (Docker Compose)
```yaml
# docker-compose.prod.yml
services:
documenso:
image: documenso/documenso:latest
ports:
- "3000:3000"
environment:
- NEXTAUTH_URL=https://sign.yourcompany.com
- NEXTAUTH_SECRET=${NEXTAUTH_SECRET} # openssl rand -hex 32
- NEXT_PRIVATE_ENCRYPTION_KEY=${ENCRYPTION_KEY}
- NEXT_PRIVATE_ENCRYPTION_SECONDARY_KEY=${ENCRYPTION_SECONDARY_KEY}
- NEXT_PUBLIC_WEBAPP_URL=https://sign.yourcompany.com
- NEXT_PRIVATE_DATABASE_URL=postgresql://documenso:${DB_PASS}@db:5432/documenso
- NEXT_PRIVATE_DIRECT_DATABASE_URL=postgresql://documenso:${DB_PASS}@db:5432/documenso
# SMTP
- NEXT_PRIVATE_SMTP_TRANSPORT=smtp-auth
- NEXT_PRIVATE_SMTP_HOST=${SMTP_HOST}
- NEXT_PRIVATE_SMTP_PORT=587
- NEXT_PRIVATE_SMTP_USERNAME=${SMTP_USER}
- NEXT_PRIVATE_SMTP_PASSWORD=${SMTP_PASS}
- NEXT_PRIVATE_SMTP_FROM_ADDRESS=signing@yourcompany.com
- NEXT_PRIVATE_SMTP_FROM_NAME=YourCompany Signing
# Signing certificate
- NEXT_PRIVATE_SIGNING_PASSPHRASE=${CERT_PASSPHRASE}
volumes:
- ./certs/signing-cert.p12:/opt/documenso/cert.p12:ro
depends_on:
db:
condition: service_healthy
restart: unless-stopped
db:
image: postgres:16-alpine
environment:
POSTGRES_USER: documenso
POSTGRES_PASSWORD: ${DB_PASS}
POSTGRES_DB: documenso
volumes:
- pgdata:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U documenso"]
interval: 5s
retries: 5
volumes:
pgdata:
```
**Important notes:**
- Documenso container runs as non-root (UID 1001) -- ensure mounted files are readable
- Prisma migrations run automatically on container start
- Documents are stored in PostgreSQL by default (fine for small-to-medium deployments)
- Use a reverse proxy (nginx, Caddy, Traefik) for SSL termination
### Step 3: AWS Lambda (API Integration)
```typescript
// lambda/signing-handler.ts
import { Documenso } from "@documenso/sdk-typescript";
import { SecretsManager } from "@aws-sdk/client-secrets-manager";
const sm = new SecretsManager({ region: "us-east-1" });
let client: Documenso;
async function getClient(): Promise<Documenso> {
if (!client) {
const secret = await sm.getSecretValue({ SecretId: "documenso/api-key" });
client = new Documenso({ apiKey: JSON.parse(secret.SecretString!).apiKey });
}
return client;
}
export async function handler(event: any) {
const documenso = await getClient();
const { title, signerEmail, signerName } = JSON.parse(event.body);
const doc = await documenso.documents.createV0({ title });
await documenso.documentsRecipients.createV0(doc.documentId, {
email: signerEmail,
name: signerName,
role: "SIGNER",
});
await documenso.documents.sendV0(doc.documentId);
return {
statusCode: 200,
body: JSON.stringify({ documentId: doc.documentId }),
};
}
```
### Step 4: Google Cloud Run
```bash
# Store secret
echo -n "$DOCUMENSO_API_KEY" | gcloud secrets create documenso-api-key --data-file=-
# Deploy
gcloud run deploy signing-service \
--image gcr.io/$PROJECT_ID/signing-service \
--platform managed \
--region us-central1 \
--set-secrets DOCUMENSO_API_KEY=documenso-api-key:latest \
--memory 256Mi \
--timeout 30s
```
### Step 5: Health Check Endpoint
```typescript
// src/health.ts — include in every deployment
app.get("/health", async (req, res) => {
try {
const client = new Documenso({ apiKey: process.env.DOCUMENSO_API_KEY! });
await client.documents.findV0({ page: 1, perPage: 1 });
res.json({ status: "healthy", service: "documenso" });
} catch (err: any) {
res.status(503).json({
status: "unhealthy",
service: "documenso",
error: err.message,
});
}
});
```
## Deployment Checklist
- [ ] API keys stored in secret manager (not env files)
- [ ] Health check endpoint configured
- [ ] HTTPS enforced (required for webhooks)
- [ ] Self-hosted: signing certificate mounted
- [ ] Self-hosted: secrets generated with `openssl rand -hex 32`
- [ ] Reverse proxy handles SSL termination
- [ ] Container runs as non-root user
- [ ] Monitoring and alerting configured
## Error Handling
| Deployment Issue | Cause | Solution |
|-----------------|-------|----------|
| Container crash on start | Missing env vars | Check all required env vars are set |
| Health check fails | API key invalid | Verify secret manager value |
| Database connection refused | Wrong connection string | Check `NEXT_PRIVATE_DATABASE_URL` |
| Signing certificate error | Wrong passphrase or path | Verify mount path and `SIGNING_PASSPHRASE` |
| Emails not sending | SMTP misconfigured | Check host/port/credentials |
## Resources
- [Documenso Self-Hosting](https://docs.documenso.com/developers/self-hosting/how-to)
- [Self-Hosting Quick Start](https://docs.documenso.com/docs/self-hosting/getting-started/quick-start)
- [Docker README](https://github.com/documenso/documenso/blob/main/docker/README.md)
- [Tips & Common Pitfalls](https://docs.documenso.com/docs/self-hosting/getting-started/tips)
## Next Steps
For webhook configuration, see `documenso-webhooks-events`.Related Skills
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
vertex-ai-deployer
Vertex Ai Deployer - Auto-activating skill for ML Deployment. Triggers on: vertex ai deployer, vertex ai deployer Part of the ML Deployment skill category.
sagemaker-endpoint-deployer
Sagemaker Endpoint Deployer - Auto-activating skill for ML Deployment. Triggers on: sagemaker endpoint deployer, sagemaker endpoint deployer Part of the ML Deployment skill category.
orchestrating-deployment-pipelines
Deploy use when you need to work with deployment and CI/CD. This skill provides deployment automation and orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
deploying-monitoring-stacks
This skill deploys monitoring stacks, including Prometheus, Grafana, and Datadog. It is used when the user needs to set up or configure monitoring infrastructure for applications or systems. The skill generates production-ready configurations, implements best practices, and supports multi-platform deployments. Use this when the user explicitly requests to deploy a monitoring stack, or mentions Prometheus, Grafana, or Datadog in the context of infrastructure setup.
deploying-machine-learning-models
This skill enables Claude to deploy machine learning models to production environments. It automates the deployment workflow, implements best practices for serving models, optimizes performance, and handles potential errors. Use this skill when the user requests to deploy a model, serve a model via an API, or put a trained model into a production environment. The skill is triggered by requests containing terms like "deploy model," "productionize model," "serve model," or "model deployment."
managing-deployment-rollbacks
Deploy use when you need to work with deployment and CI/CD. This skill provides deployment automation and orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
kubernetes-deployment-creator
Kubernetes Deployment Creator - Auto-activating skill for DevOps Advanced. Triggers on: kubernetes deployment creator, kubernetes deployment creator Part of the DevOps Advanced skill category.
integration-test-setup
Integration Test Setup - Auto-activating skill for Test Automation. Triggers on: integration test setup, integration test setup Part of the Test Automation skill category.
running-integration-tests
This skill enables Claude to run and manage integration test suites. It automates environment setup, database seeding, service orchestration, and cleanup. Use this skill when the user asks to "run integration tests", "execute integration tests", or any command that implies running integration tests for a project, including specifying particular test suites or options like code coverage. It is triggered by phrases such as "/run-integration", "/rit", or requests mentioning "integration tests". The plugin handles database creation, migrations, seeding, and dependent service management.
integration-test-generator
Integration Test Generator - Auto-activating skill for API Integration. Triggers on: integration test generator, integration test generator Part of the API Integration skill category.
fathom-ci-integration
Test Fathom integrations in CI/CD pipelines. Trigger with phrases like "fathom CI", "fathom github actions", "test fathom pipeline".