-
1.) Back up CLARITY_DNN_UAT (get that file path for the backup and paste into directory where PROD_SIM’s backups are on the prod database 10.100.250.3)
-
2.) Restore it to PROD_SIM (10.100.250.3)
-
Name is CLARITY_DNN_PROD_SIM_YYYYMMDD
-
3.) Rename original PROD_SIM db to Z_CLARITY_DNN_PROD_SIMYYYMMDD
- Need to stop PROD_SIM site in order to rename DB
-
4.) Turn back on app pool for PROD_SIM
-
5.) Run crawler against PROD_SIM site on remote dev server (10.100.250.1)
- Make sure PROD_SIM host entry is pointing to 10.100.250.1
- ALWAYS MAKE SURE IIS ISN'T POINTED TO SITE WITH CACHED FILES BEFORE CRAWLING. YOU WILL GET INCORRECT CACHED FILES!
-
6.) Copy static html file FOLDERS returned from crawl and copy into newly named folder (named after current date) into \\2019-file-1\Clarity\Clarity Ventures\CVI - Clarity Ventures - General\_archive\
-
7.) Create a copy of the most recent live folder on prod server (it's recommended to use command line for this as copying files/folders is faster)
- Check connection strings
-
8.) Paste crawled folders from archive into copied site (overwrite existing directories)
- Point PROD_SIM to the copied live site of PROD.
- QA of the site can start after the crawled files have been
pasted into the copied site
-
9.) Run PageSpeed against PROD_SIM with cached files newly copied into it.
-
10.) Once we know the crawl has run successfully, we back up PROD_SIM db to PROD db.
-
11.) Make sure robots.txt isn’t disallowing all
-
12.) For screaming frog – make sure site is pointed to prod for first run of SF
-
Make sure host entry is pointed to 10.100.20.101 (prod server)
For second run of screaming frog- point clarity-ventures site back to 10.100.250.1
-
Then pointed to local dev when running crawler. Then point back to prod for second crawl after changes have been made.
- What changes are needed before crawl of PROD?
-
13.) Compare pre and post crawls (is this SF "crawl" or Clarity Crawl?) to make sure there aren’t more errors.
- Use vlookup to check for differences in URLs
- Now, there's a comparison option in SF that we can hopefully get the same results from
-
14.) Pull backup from production
- Restore to local and push git repo updates
-
15a.) Pull into stage and ensure completely matching prod
- 1. Run screaming frog against stage and prod to get a baseline to confirm the same
- 2. Run PSI to validate as well
- 3. Push once validated
-
15b.) Validate that data from UAT => Prod_Sim and eventually Prod *?
- 1. Run export script for proper date range within DNN
- 2. Export data and run import to Prod_SimS and then Prod (later)
- 3. Ensure tabnames and easydnnnews titlelinks are lowered
-
16.) Pull changes from Aaron and Justin into stage
- 1. Resolve any issues via process of running SF, and PSI
- 2. Run unused CSS and attempt to identify a full list of pages and sections that are materially different re: skins and incorporate into landing pages within unused css tool *(do we still use Unused CSS?)
- 3. Update to resolve the jquery issue throughout the site and validate
- 4. Ensure PSI and SF show passing results 5. Push to stage branch
-
17.) Updates to modules
- 1. Ensure sitemap module bringing in all pages (including Glossary and any other additional pages)
- 2. Run sitemap.xml generator and ensure working as expected
-
18.) Work through all issues from aHrefs, Moz, and screaming frog
- 1. URL issues
- 2. Meta-Data issues
- 3. Performance issues where possible
- 1. PSI - issues with CLS
- 2. PSI - issues with LCP
- 3. Other issues?
- 4. Other items in general
- 1. JS compression and resolution
- 2. CSS compression and resolution
- 3. Image compression and resolution
- 5. Ensure PSI and SF show passing results
- 6. Push to stage branch
-
19.) Backup UAT and ensure DBs backed up too
-
20.) Push all changes into UAT and confirm deployed
- Validate for any issues and resolve using SF and PSI
- Push to uat branch
-
21.) Run crawler and re-validate
- Validate with SF and PSI
- Push to uat branch
-
22.) Push to production with full round of updates
- Push to prod branch
- Validate with SF and PSI
- Remember to remove robots.txt disallow statement
- Ensure DBs are both located on Prod Marketing SQL
- Validate that prod marketing SQL is updated as expected
-
23.) Send note to the team to review and validate based on their findings as well
- Pull DB down from prod for DNN and Custom and ensure kept up to date