Deployment

Multi-node, high-availability Pigsty deployment for serious production environments.

Unlike Getting Started, production Pigsty deployments require more Architecture Planning and Preparation.

This chapter helps you understand the complete deployment process and provides best practices for production environments.


Before deploying to production, we recommend testing in Pigsty’s Sandbox to fully understand the workflow. Use Vagrant to create a local 4-node sandbox, or leverage Terraform to provision larger simulation environments in the cloud.

pigsty-sandbox

For production, you typically need at least three nodes for high availability. You should understand Pigsty’s core Concepts and common administration procedures, including Configuration, Ansible Playbooks, and Security Hardening for enterprise compliance.


Install Pigsty for Production

How to install Pigsty on Linux hosts for production?

Prepare Resources for Serious Deployment

Production deployment preparation including hardware, nodes, disks, network, VIP, domain, software, and filesystem requirements.

Planning Architecture and Nodes

How many nodes? Which modules need HA? How to plan based on available resources and requirements?

Setup Admin User and Privileges

Admin user, sudo, SSH, accessibility verification, and firewall configuration

Sandbox

4-node sandbox environment for learning, testing, and demonstration

Vagrant

Create local virtual machine environment with Vagrant

Terraform

Create virtual machine environment on public cloud with Terraform

Security

Security considerations for production Pigsty deployment


Last modified 2026-01-06: batch update (cc9e058)