Deploying to Cloud Providers
Host your templates on popular cloud providers using their standard workflows.
Overview
You can deploy your blog or docs templates to any platform that can host a React or static site.
Vercel
Deploy to Vercel with Git-based deployments and automatic previews.
Setup
- Push your template to GitHub
- Go to vercel.com
- Import your repository
- Configure environment variables
- Deploy
Environment Variables
INKPILOTS_API_KEY=your_api_key
INKPILOTS_WORKSPACE_ID=your_workspace_id
Features
- ✓ Automatic HTTPS
- ✓ Preview deployments
- ✓ Edge functions
- ✓ Analytics
- ✓ Custom domains
Netlify
Use Netlify for simple static hosting with built-in CI/CD.
Setup
- Push your template to GitHub
- Go to netlify.com
- Import your repository
- Set build command: npm run build
- Set publish directory: .next or out
- Deploy
Environment Variables
Add in Netlify dashboard under Site Settings > Environment Variables.
Features
- ✓ Continuous deployment
- ✓ Form handling
- ✓ Serverless functions
- ✓ Split testing
- ✓ Custom domains
AWS Amplify
Deploy to AWS with full cloud infrastructure.
Setup
# Install Amplify CLI
npm install -g @aws-amplify/cli
# Initialize
amplify init
# Add hosting
amplify add hosting
# Deploy
amplify publish
Features
- ✓ Full AWS integration
- ✓ Authentication
- ✓ API (GraphQL/REST)
- ✓ Storage
- ✓ Global CDN
Custom Infrastructure
Bring your own infrastructure on AWS, Azure, or other providers using container or static hosting.
Docker Deployment
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build
FROM node:20-alpine AS runner
WORKDIR /app
COPY --from=builder /app/.next/standalone ./
COPY --from=builder /app/.next/static ./.next/static
COPY --from=builder /app/public ./public
EXPOSE 3000
CMD ["node", "server.js"]
Static Export
For static hosting (S3, Azure Blob, etc.):
# Add to next.config.js
output: 'export'
# Build
npm run build
# Upload 'out' directory to your host
Domain Configuration
Custom Domain Setup
- Add domain in hosting provider
- Update DNS records:
- A record: @ → hosting IP
- CNAME: www → hosting domain
- Wait for DNS propagation
- Enable HTTPS
Best Practices
- Use environment variables - Never commit secrets
- Enable caching - Improve performance
- Set up monitoring - Track errors and performance
- Configure redirects - Handle old URLs
- Test before production - Use preview deployments