-
Notifications
You must be signed in to change notification settings - Fork 43
Deployment Setup
Justin Chadwell edited this page Jul 10, 2020
·
2 revisions
Our development/deployment setup is a little scattered, like all setups out there, but it means you'll need to access a variety of services to do things.
-
Source control: GitHub
- All of our code is hosted on GitHub
- If you're not familiar with Git, definitely try and learn it
-
Hosting: GitHub pages
- We use the GitHub default, GitHub pages
- It automatically builds the Jekyll site and deploys it (and listens on
the domain name) in the
CNAME
file
-
CI/CD: GitHub pages/Netlify
- GitHub pages is used to deploy our production site
- Netlify is used to deploy our branch previews (at <cssbham.netlify.app>(https://cssbham.netlify.app))
-
DNS: Namecheap
- The domain name is owned by Tom, so if you need new DNS records, bother him to do it
- As long as we remain with GitHub Pages, we shouldn't need different records
There are a few accounts associated with all this.
-
CSSUoB GitHub Organization
- The group that we do all GitHub stuff under
- Can have multiple members and fine-grained permissions for members
- We have a few repos, namely, the site, and a few other resources
- The organization owns the CSS Admin Portal OAuth App
-
CSS GitHub Account
- Super confusingly, we also have a CSS GitHub account
- This is a bit of a hack to allow Netlify to access the CSS repos without being directly tied to an individual user's OAuth
- CSS Netlify
- This account is used to access the Netlify settings and such
- The Admin Portal OAuth settings are copied from the organization to here