Deploy RudderStack Data Plane on Your Own Server

**Deploy your self-hosted RudderStack Open Source instance on Senate.** This template will automatically set up the following services: - RudderStack Server (Backend): The core data processing engine. - PostgreSQL Database: Stores job metadata and other operational data. - RudderStack Transformer: Handles data transformations for selected destinations. - StatsD Metrics Exporter: For exposing application metrics. **Configuration Notes:** 1. **Workspace Token (Required):** You MUST provide your RudderStack Workspace Token. You can find this in your RudderStack control plane (e.g., app.rudderstack.com). 2. **PostgreSQL Password:** A strong password for the database will be auto-generated. You can override it if necessary. 3. **Image Versions:** Default versions are set to 'latest'. For production environments, it is highly recommended to specify stable, numerical version tags for both Rudder Server and Rudder Transformer. **Important Note on PostgreSQL `shm_size`:** The original Docker Compose for RudderStack specifies `shm_size: 128mb` for the PostgreSQL container. This YAML template for Senate does not directly set this Docker-specific option as `captainVersion: 4` templates typically focus on higher-level configurations. - For many use cases, the default Docker shared memory size (often 64MB) may be sufficient. - If you encounter performance issues or errors with the PostgreSQL service (`${app_name}-db`), especially under heavy load or with numerous connections, you might need to increase the `shm_size` available to Docker containers. This is generally configured at the Docker daemon level on your Senate worker node(s). Please consult your Docker and OS documentation for instructions on how to adjust this setting.