Local banzai setup for running at site

[timbeccue]

Changes in service of #422

This PR introduces the local setup we'll use for site deployments of banzai, sans calibration caching which will be added in a subsequent PR.

Local Banzai Notes

To run:

docker compose -f docker-compose-site.yml --env-file .site-banzai-env up -d --build

This requires an env file called .site-banzai-env that should look like this:

# .site-banzai-env

# Database Configuration
DB_ADDRESS=sqlite:////data/banzai.db    # Path for the docker container, not the host.
CAL_DB_ADDRESS=""                       # This should be the address to the AWS banzai database where we get calibrations
SITE_ID=

# API Configuration
API_ROOT=https://archive-api.lco.global/
AUTH_TOKEN=

# Data Paths
HOST_DATA_DIR=./site_banzai # this maps to /data in the container, and should contain unprocessed data in a subdirectory `raw`
HOST_PROCESSED_DIR=./site_banzai/output # path where processed data will be saved on the host

# Container Networking
FITS_BROKER=rabbitmq
FITS_BROKER_URL=amqp://rabbitmq:5672
FITS_EXCHANGE=fits_files
TASK_HOST=redis://redis:6379/0

# Celery Configuration
CELERY_TASK_QUEUE_NAME=e2e_task_queue
CELERY_LARGE_TASK_QUEUE_NAME=e2e_large_task_queue

# Worker Configuration
BANZAI_WORKER_LOGLEVEL=debug
OMP_NUM_THREADS=2
OPENTSDB_PYTHON_METRICS_TEST_MODE=1

In order to send images to be processed, run:

python queue_images.py <host_data_dir>/raw

The data to be processed should be in the directory ${HOST_DATA_DIR}/raw. The output will be saved in ./${HOST_PROCESSED_DIR}.

[timbeccue]

Is the prior docker-compose.yml file important to preserve? If not, I'll replace it with my version, currently docker-compose.local.yml