Reference ========= .. _environment-variables: Environment variables --------------------- See `OCP's approach to Django settings `__. New variables are: LOG_LEVEL The log level of the root logger Collect task ~~~~~~~~~~~~ This project communicates with Kingfisher Collect via Scrapyd. However, Scrapyd has no endpoint for deleting data, so ``KINGFISHER_COLLECT_FILES_STORE`` is needed. SCRAPYD_URL The base URL of Scrapyd, for example: ``http://localhost:6800`` SCRAPYD_PROJECT The project within Scrapyd KINGFISHER_COLLECT_FILES_STORE The directory from which to **delete** the files written by Kingfisher Collect. If Kingfisher Collect and Kingfisher Process share a filesystem, this will be the same value for both services. Process task ~~~~~~~~~~~~ This project communicates with Kingfisher Process via its `API `__. KINGFISHER_PROCESS_URL The base URL of Kingfisher Process .. _env-exporter-flattener: Exporter and Flattener tasks ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ :ref:`cli-exporter` reads compiled releases directly from Kingfisher Process' database (like `Pelican backend `__). RABBIT_URL The `connection string `__ for RabbitMQ RABBIT_EXCHANGE_NAME The name of the RabbitMQ exchange. Follow the pattern ``kingfisher_process_{service}_{environment}`` like ``kingfisher_process_data_registry_production`` KINGFISHER_PROCESS_DATABASE_URL The `connection string `__ for Kingfisher Process's database EXPORTER_DIR The directory to which the ``exporter`` app writes files Spoonbill integration ~~~~~~~~~~~~~~~~~~~~~ SPOONBILL_URL The base URL of Spoonbill SPOONBILL_API_USERNAME The username for `basic HTTP authentication `__ SPOONBILL_API_PASSWORD The password for basic HTTP authentication SPOONBILL_EXPORTER_DIR The directory to which the ``exporter`` app writes files, from Spoonbill's perspective. This is relevant if this project or Spoonbill is running in a container.