Deploying sites from dotCMS

This guideline list out all the steps involve to deploy a site from dotCMS.

Step 1: Push Publishing from dotCMS to AWS

1. When a page/file is completed in forCMS, it needs to be saved and published.
2. Before push publishing to AWS, it is a good practice to republish the pages/files we want to push.
   • 
3. Select Push Publish to push the required files to AWS temporary folder. This folder stores all static HTML, JS, CSS, Assets exported from dotCMS.
   • 
4. In the Push Publish popup windows, select the correct branch to push to. The branch without a client code at the end is used for all internal sites. Otherwise please push to the branch with correct client code.
   • 
5. Once the files are pushed, the status can be monitored in Site Browser > Publishing Queue
   • 

Step 2: Deploy to Test Environment

1. To deploy the sites you have just pushed from CMS, you need to have access to Jenkins, with an interface called EZ Deployment at http://54.245.8.122:8085
2. You need to have your IP address whitelisted to be able to access the server. Please contact IT Support if you don't have it yet.
   • 
3. When deploying to Test Environment, Jenkins downloads all the static files we pushed to Temporary AWS folder in Step 1, re-builds them to a desired structure, optimizes for performance, then upload the new files to Test bucket in AWS.
4. In homepage after login, select Execute on the project you want to deploy, e.g. EuphoricFeet.
   • 
5. System will show a popup with 2 parameters to select.
   • 
6. Select the Environment from the dropdown, in this case is Test, then select the folder you want to deploy (e.g. EN), then click Execute to start the process.
7. Once the process is completed, you can check the test domain, structure as test.yourdomain.com

Step 3: Deploy to Live Environment

1. Perform the same steps as deploying to Test Environment, but select "Live" in Environment dropdown.
2. When deploying to Live environment, Jenkins simply copies everything from the Test bucket in AWS over to the Live bucket. It ensures that new changes pushed from dotCMS but not yet deployed to Test Environment for verification will not get to the Live Environment.
3. Once the process is completed, you can check the test domain, structure as www.yourdomain.com