-
Notifications
You must be signed in to change notification settings - Fork 1
Locally Develop CMS and TUP CMS
In Core-CMS make changes. Build a CMS image. In client repo, use the CMS image snapshot.
First, In Core-CMS Clone
Build and save a CMS container image.
Build a CMS Image Remotely (Requires Access)
Follow (internal) How To Docs - How To Build & Deploy a CMS Website - Core-CMS.
Build a CMS Image Locally (More Steps)
Note If another CMS container is running, shut it down.
Important If you have changed any dependencies (e.g. Locally Develop CMS and Styles), pin those changes via appropriate lock file (e.g.
npm install --save …
); otherwise thebuild
step will overwrite those changes.
-
docker-compose -f docker-compose.dev.yml build --build-arg BUILD_ID="my-local-build-N"
Wheremy-local-build
should be unique each time, to trigger a new stylesheet build. docker-compose -f docker-compose.dev.yml up --detach
docker exec -it core_cms sh -c "python manage.py collectstatic --no-input"
- (optional) Verify your change is present on your Core-CMS.
-
docker commit core_cms
The output (with or withoutsha256:
) is your__IMAGE_ID__
. -
docker tag __IMAGE_ID__ __LOCAL_TAG_NAME__
You may choose any name you would like for__LOCAL_TAG_NAME__
. docker-compose -f docker-compose.dev.yml stop
The container snapshot steps are a streamlined version of (internal) How to Create Docker Image from Local Container.
Use the CMS container image.
Note If another CMS container is running, shut it down.
- Open
apps/tup-cms/Dockerfile
for editing. - Change
FROM taccwma/core-cms:...
toFROM __LOCAL_TAG_NAME__
.
Or the tag name of any other image you want to test. docker-compose -f apps/tup-cms/docker-compose.dev.yml build --no-cache
npx nx serve tup-cms
- Verify your change is present.
Undocumented.
a Different Client of Core-CMS
Refer to client repo documentation.
TACC ACI WMA Core-CMS Project Documentation