Skip to main content

Infrastructure Prompts

Ready-to-use prompts for server provisioning, deployment, configuration, and maintenance tasks using Pacing Agency's infrastructure stack.

Overview​

These prompts help you quickly set up and maintain our infrastructure:

  • Hetzner Cloud servers for self-hosted services
  • n8n workflow automation
  • Cloudflare DNS, SSL, and CDN configuration
  • Docker Compose service deployments
  • SSL certificates with Let's Encrypt

Infrastructure Stack​

Our self-hosted infrastructure runs on:

  • Hosting: Hetzner Cloud (Germany datacenters)
  • Orchestration: Docker Compose
  • Automation: n8n workflows
  • DNS/CDN: Cloudflare
  • SSL: Let's Encrypt (automated renewal)
  • Monitoring: Built-in health checks and alerts

Available Prompts​

Server Provisioning​

Hetzner New Server Setup
Provision a new Hetzner Cloud server with security hardening, Docker, and backups.

Use for: Setting up new services (n8n, TwentyCRM, Notifuse, Remark42, etc.)
Time: 30 minutes
Difficulty: Intermediate

Automation & Workflows​

n8n New Workflow
Create a new n8n workflow with error handling, testing, and documentation.

Use for: Webflow webhooks, Twilio processing, Google Ads conversions, CircleLoop calls
Time: 20 minutes
Difficulty: Beginner

DNS & Security​

Cloudflare DNS Setup
Configure DNS records, proxy settings, SSL/TLS, page rules, and caching.

Use for: New domains, subdomain setup, moving to Cloudflare
Time: 15 minutes
Difficulty: Beginner

Service Deployment​

Docker Compose Service
Set up a new service using Docker Compose with proper configuration, volumes, and networking.

Use for: Deploying new tools or client services
Time: 25 minutes
Difficulty: Intermediate

SSL & Certificates​

SSL Certificate Renewal
Renew SSL certificates using Let's Encrypt and verify configuration.

Use for: Certificate expiry warnings, domain changes
Time: 10 minutes
Difficulty: Beginner

Quick Start Guide​

1. Choose Your Task​

Identify what you need to accomplish:

  • New service? → Start with Hetzner New Server Setup
  • Automation needed? → Use n8n New Workflow
  • Domain setup? → Use Cloudflare DNS Setup
  • Deploying app? → Use Docker Compose Service
  • Certificate issue? → Use SSL Certificate Renewal

2. Gather Prerequisites​

Before using any infrastructure prompt, ensure you have:

  • Access to relevant accounts (Hetzner, Cloudflare, etc.)
  • Project specifications (server size, location, etc.)
  • Budget approval (if creating billable resources)
  • Understanding of the service purpose

3. Customize the Prompt​

Replace these common placeholders:

  • [PROJECT_NAME] - Hetzner project or service name
  • [SERVER_PURPOSE] - What this server/service does
  • [DATACENTER] - Location (Falkenstein/Nuremberg/Helsinki)
  • [SERVER_TYPE] - Size (CPX11/CPX21/CPX31)
  • [DOMAIN] - Domain or subdomain to configure

4. Follow Up​

After deploying infrastructure:

  1. Document in tool docs - Update relevant .md file in tools/
  2. Add to monitoring - Ensure health checks are configured
  3. Update team access - Document who has access
  4. Schedule backup checks - Verify backups are working

Common Infrastructure Patterns​

Pattern 1: New Self-Hosted Service​

Typical workflow for deploying a new self-hosted service:

Prompts to use:

  1. Hetzner New Server Setup
  2. Cloudflare DNS Setup
  3. Docker Compose Service
  4. SSL Certificate Renewal (if needed)

Example: Setting up a new Remark42 comments server

Pattern 2: Client Website Infrastructure​

Typical workflow for client website infrastructure:

Prompts to use:

  1. Cloudflare DNS Setup
  2. SSL Certificate Renewal (if custom)

Example: Onboarding a new Webflow client

Pattern 3: Automation Workflow​

Typical workflow for creating automation:

Prompts to use:

  1. n8n New Workflow

Example: Webflow form submission → TwentyCRM integration

Infrastructure Best Practices​

Security​

  • ✅ Use strong SSH keys (ED25519 or RSA 4096)
  • ✅ Configure firewall rules (limit to necessary ports)
  • ✅ Keep systems updated (automated updates where possible)
  • ✅ Use SSL/TLS for all public endpoints
  • ✅ Regular backup verification
  • ❌ Never expose unnecessary ports
  • ❌ Don't use default passwords
  • ❌ Avoid root SSH access

Performance​

  • ✅ Right-size servers (don't over-provision)
  • ✅ Use appropriate datacenter (EU for European clients)
  • ✅ Enable Cloudflare caching where appropriate
  • ✅ Monitor resource usage
  • ✅ Set up alerts for capacity issues
  • ❌ Don't ignore performance warnings
  • ❌ Avoid putting everything on one server

Reliability​

  • ✅ Enable automatic backups
  • ✅ Test disaster recovery procedures
  • ✅ Use health checks for services
  • ✅ Have rollback procedures documented
  • ✅ Monitor uptime and errors
  • ❌ Don't deploy without testing
  • ❌ Avoid single points of failure

Documentation​

  • ✅ Document all infrastructure in tool docs
  • ✅ Keep architecture.md up to date
  • ✅ Note all configuration changes
  • ✅ Track costs and renewals
  • ✅ Document team access
  • ❌ Don't assume someone else documented it
  • ❌ Avoid tribal knowledge

Current Infrastructure​

See our live infrastructure in:

Troubleshooting Common Issues​

Server Provisioning​

Issue: SSH connection refused after provisioning
Solution: Check firewall rules allow port 22, verify SSH key is correct

Issue: Docker installation fails
Solution: Ensure using Ubuntu 24.04 LTS, check internet connectivity

DNS Configuration​

Issue: DNS not resolving
Solution: Wait 5-10 minutes for propagation, verify CNAME/A record is correct

Issue: SSL certificate errors
Solution: Verify DNS is pointing to Cloudflare (orange cloud), check SSL/TLS mode

Docker Deployment​

Issue: Container won't start
Solution: Check logs (docker logs [container]), verify environment variables

Issue: Port already in use
Solution: Check for conflicting services, change port in docker-compose.yml

n8n Workflows​

Issue: Workflow execution fails
Solution: Check credentials are valid, test individual nodes, review error logs

Issue: Webhook not triggering
Solution: Verify webhook URL is accessible, check n8n is running, test manually

Contributing New Prompts​

Have a new infrastructure task that needs a prompt?

  1. Follow the prompt template structure
  2. Test the prompt on a real infrastructure task
  3. Document common issues you encountered
  4. Add to the appropriate category
  5. Share with the team for feedback

Remember: Always test infrastructure changes in a staging environment first. Never deploy critical infrastructure changes during peak hours or without a rollback plan.