You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is tracking the Non-Prod deployment for Django version of CCM. We will have 2 new Openshift development project called
ccm-test ---> Canvas Test
ccm-beta ---> Canvas beta
The Database doesn't change so no need to request a new database, we will map the database schema by creating new model
Choosing a new URL or reusing an existing one will be a question to thinking about. With reusing the existing one we need to do a DNS cutover pointing to newly created openshift project. so this is all fine in non-prod, but on the prod launch day this could wait and watch.
We want the new Project since that is easier to manage and maintain the existence node during the transition period.
The text was updated successfully, but these errors were encountered:
This issue is tracking the Non-Prod deployment for Django version of CCM. We will have 2 new Openshift development project called
ccm-test ---> Canvas Test
ccm-beta ---> Canvas beta
The Database doesn't change so no need to request a new database, we will map the database schema by creating new model
Choosing a new URL or reusing an existing one will be a question to thinking about. With reusing the existing one we need to do a DNS cutover pointing to newly created openshift project. so this is all fine in non-prod, but on the prod launch day this could wait and watch.
We want the new Project since that is easier to manage and maintain the existence node during the transition period.
The text was updated successfully, but these errors were encountered: