-
Notifications
You must be signed in to change notification settings - Fork 1
How to Use a Custom Docker Compose File
W. Bomar edited this page Dec 9, 2021
·
4 revisions
- 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.
- Copy
docker-compose.dev.yml
asdocker-compose.custom.yml
. - In the
docker-compose.custom.yml
file, replacecore_cms
withsad_cms
*, e.g.:-
core_cms
→sad_cms
-
core_cms_postgres
→sad_cms_postgres
-
core_cms_postgres_data
→sad_cms_postgres_data
- ...
-
- (If no
taccsite_cms/secrets.py
file),- Create
taccsite_cms/secrets.py
. - Copy
DATABASES = { ... }
fromtaccsite_cms/settings.py
totaccsite_cms/secrets.py
.
- Create
- In the
taccsite_cms/secrets.py
file, replace "core_cms_postgres" with "sad_cms_postgres".
Footnotes
* The sad_
prefix means "Stand-Alone Django". It is used in other documents (like Locally Develop CMS + Portal + Docs). You may use another prefix.
TACC ACI WMA Core-CMS Project Documentation