This repository contains Docker Compose configuration for running OpenCue components.
- Cuebot: Core OpenCue service for job management
- PostgreSQL: Database for storing OpenCue data
- Git
- Docker
- Clone this repository
- Run the start script:
chmod +x *.sh
./start-cuebot.shThe script will:
- Check if
docker.envexists - If not, prompt you to configure ports (or use defaults)
- Create a
docker.envfile with your settings - Start the PostgreSQL service
- Ask if you want to initialize the database schema and seed data (recommended for first-time setup)
- Start the Cuebot service
- Verify the services are running:
docker-compose psThe first time you run the system, you need to initialize the database schema and seed data. The start script will ask if you want to do this automatically. If you need to do it separately, you can run:
./setup-db.shThis will:
- Download the official OpenCue schema (v1.4.11) from GitHub releases
- Download the official seed data (v1.4.11) from GitHub releases
- Apply both to your PostgreSQL instance
- Create a test show and other necessary initial data
You can customize the environment variables by:
- Editing the generated
docker.envfile - Creating your own
docker.envbased ondocker.env.examplebefore running the start script
Default configuration in docker.env.example:
- PostgreSQL
- Database:
cuebot_local - Username:
cuebot - Password:
changeme
- Database:
- Ports
- Cuebot HTTP: 8080
- Cuebot HTTPS: 8443
- PostgreSQL: 5432
Default ports (can be configured during setup):
- Cuebot HTTP: 8080
- Cuebot HTTPS: 8443
- PostgreSQL: 5432
The following data is persisted using Docker volumes:
postgres_data: PostgreSQL databaseopencue_logs: OpenCue logs
./stop-cuebot.shAlternatively, you can use:
docker-compose downTo completely remove the services and volumes:
docker-compose down -vIf you encounter any issues with the setup:
./fix-connection.shThis script will:
- Stop all services
- Reset your docker.env to default values
- Restart services in the correct order
- Reinitialize the database if requested
If Cuebot can't connect to PostgreSQL:
-
Make sure the PostgreSQL container is running:
docker ps | grep postgres -
Check PostgreSQL logs:
docker logs opencue-postgres
-
Check Cuebot logs:
docker logs opencue-cuebot
-
Run the debug script to diagnose issues:
./debug.sh
If you see "address already in use" errors, you can:
- Use different ports when prompted during setup
- Manually edit the
docker.envfile to change ports - Stop any running instances of PostgreSQL:
sudo systemctl stop postgresql