1. DEPLOY

Deploying the site

The site automatically builds twice every day which updates the latest data from Craft.

The release/deploy updates the data and the code. Which is NOT done automatically. When we want to release/deploy (update the data and the code) this site;
follow these steps

• Deploying from a tagged release
• Manual Deploy to update data ie: Courtney Hoffner:
  • Comms needs to push a site update because SRLF had to close unexpectedly.
  • Comms needs to trigger a website build.
  • Comms needs to push a site update due to the power outage at the Management Library.

---

Deploying from a tagged release

1. Click on +101 releases (whatever the number it is at the time of your proposed release)

It will look something like this:

---

2. Click the pencil icon on the right
   You will see something like this.
   You probably do not need to change anything.
   It will reflect all the work that has been done since the last release.
   It will update the release number using semantic versioning based on the types of changes that were made.

---

3. Click Publish release This will

• deploy a build of the newly published release to production (prod) You do not have to also do a manual build.

---

The test server always points to what is merged in main.

---

Manual Deploy to update data

When you see a message like this in softwaredev-website

Courtney Hoffner
Hi Comms needs to push a site update because SRLF had to close unexpectedly. Can one of you help with this?

Hi Comms needs to push a site update due to the power outage at the Management Library.

Hi Comms needs to push a site update because there's an event on campus affecting access to Powell.

---

1. Click on Actions

---

2. Click on Manually rebuild and deploy static site

---

3. Click Run workflow

---

4. Find the latest tagged release under Use workflow from

---

5. Set the Environment to prod

---

6. Click Run workflow

---

-43a2268a20e3) -1379b95cae65)