deploy-production

Deploy the Renfield codebase to on-premises servers with rsync and Docker Compose.

34|5|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/ebongard/renfield --skill deploy-production
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-production
Source: https://github.com/ebongard/renfield/tree/main/.claude/skills/deploy-production
Command: npx skills add https://github.com/ebongard/renfield --skill deploy-production

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a clear, safety-first process to deploy the Renfield application to production servers while preventing device bricking, accidental secret leakage, and incorrect production frontend builds.

Core Features & Use Cases

  • Safe file synchronization that excludes secrets and development artifacts, minimizing risk during code syncs to production.
  • CPU-only backend rebuild workflow using Docker Compose for servers without GPUs and explicit instructions for building the frontend with a production target.
  • Production secrets management guidance using file-based Docker secrets and Pydantic settings, plus satellite provisioning rules and ansible playbook usage to avoid SD card corruption on Pi Zero 2 W devices.
  • Use Case: Deploy application updates to renfield.local, run database migrations, and provision or update voice satellites while avoiding service restarts that can brick devices.

Quick Start

Deploy Renfield to renfield.local by syncing code without secrets, rebuilding the backend with docker compose on the server, and building the frontend on the server using the production build target.

Frequently Asked Questions about deploy-production

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy to production servers safely without leaking secrets?

Safe production deployment uses rsync synchronization configured to exclude secrets and development artifacts, minimizing accidental secret leakage during code syncs to remote hosts.

Can I use Docker Compose for backend rebuilds on CPU-only servers without GPUs?

Docker Compose supports backend rebuilds on CPU-only production hosts without GPUs, providing a controlled workflow for deploying application updates to on-premises servers.

How do I build the frontend with a production target during deployment?

Building the frontend with a production target requires running the build process directly on the server after code synchronization and backend rebuild steps are completed.

What's the best way to provision Raspberry Pi satellite devices without bricking them?

Satellite provisioning for Raspberry Pi devices follows documented rules and ansible playbook usage to avoid SD card corruption and prevent service restarts that can brick Pi Zero 2 W devices.

How does file-based secrets management work with Docker and Pydantic settings?

File-based Docker secrets combined with Pydantic settings keep production secrets managed through mounted files rather than environment variables, maintaining security on the deployment server.

Why does rsync exclude development artifacts during production deployment?

Rsync excludes development artifacts and secret files during production deployment to prevent unnecessary files from reaching the server and to reduce the risk of exposing sensitive configuration data.