How to Use a Custom Docker Compose File

Purpose

• To avoid conflict when running https://github.com/TACC/Core-Portal/ and https://github.com/TACC/Core-CMS/ locally.
• (Advanced) To run multiple CMS instances simultaneously on one machine.

Steps

1. Copy docker-compose.dev.yml as docker-compose.custom.yml.
2. In the docker-compose.custom.yml file, replace core_cms with sad_cms*, e.g.:
   • core_cms → sad_cms
   • core_cms_postgres → sad_cms_postgres
   • core_cms_postgres_data → sad_cms_postgres_data
   • ...
3. (If no taccsite_cms/secrets.py file),
   1. Create taccsite_cms/secrets.py.
   2. Copy DATABASES = { ... } from taccsite_cms/settings.py to taccsite_cms/secrets.py.
4. In the taccsite_cms/secrets.py file, replace "core_cms_postgres" with "sad_cms_postgres".

---

^{* The prefix is not required to be sad_. You may use another prefix. The sad_ stands for "Stand-Alone Django", and is used in other documents (like Locally Develop CMS + Portal + Docs).}