Create two test sites (one for master hjckrrh, one for next hjckrrh) for demo days

[mmafe]

Create two test sites (one for master, one for next) for demo days.

Mandatory

• [x] Create /master pointing to aoda.test.web.uoguelph.ca/aoda directory (running master branch)
• [x] Create /next pointing to aoda.test.web.uoguelph.ca/aoda-next directory (running next branch)
• [x] Add both sites to Lumturio
• [x] Turn on the UG testing module
• [x] Set up the following roles: author, editor, sitemanager with passwords (add to Keepass)

For now, if you wish to update the branch on those sites:

1. On the AODA test server, go to the /var/www/html/aoda.test.web.uoguelph.ca/
2. If you wish to update the next site, go to aoda-next. If you wish to update the master site, go to aoda
3. Type: git fetch origin
4. Type: git status to confirm you are on the branch you think you are
5. Type: git pull origin <branch-name>
   • should be master in the aoda directory
   • should be next in the aoda-next directory

Running tests during demo: You will need to:

• update your environment.js files with baseURL and credentials for the site you wish to test (i.e. master or next). This might also mean updating the roles credentials as well if they're being used.
• ensure that you're the only one running tests on this site.
• run testcafe off your regular machine anyway

Significant Flaw with this idea: If two people are running tests on these sites at the same time, they might both be creating content, adding viewpanes, etc. at the same time, which could cause tests to fail. Starting to think this is not a great solution for us running tests. Ideally the site would be created and destroyed as part of running the tests, and that is not going to happen in the scope of this issue.

Regarding Webhooks: The webhooks were not as straight-forward as I thought they would be. Rather than figure out how to update the web gateway and get the AODA test server listening for the github webhook this sprint, I'm moving that into the out of scope pile. It even sounds like something that might fit under the DevOps goals that Web & Dev Solutions might be looking into, but definitely a larger scale problem to solve than this issue. :)

Note: Was going to try Pantheon, but Pantheon does not support Webhooks.

Possible Items for later

• Hook Update process so ws-securehst18 would listen for web hook
  • Hook 1 - When next branch is updated on github, next branch is pushed to aoda.test.web.uoguelph.ca/aoda-next directory
  • Hook 2 - When master branch is updated on github, master branch is pushed to aoda.test.web.uoguelph.ca/aoda directory
• Should be able to recreate the site from scratch and have the following automatically taken care of:
  • Roles set up by the script
  • Turn on the UG testing
  • Turn on System Status (folks will need to update Lumturio if they recreate the site)
• Could run testcafe directly on ws-securehst18;