search

DDMAL / linkedmusic-website

website for LinkedMusic Partnership Grant
https://linkedmusic.ca
2 stars 0 forks source link

set up hosting with github pages #10

Closed emilyhopkins closed 3 years ago

emilyhopkins commented 3 years ago

serve site as-is with GitHub pages

emilyhopkins commented 3 years ago

https://docs.github.com/en/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll

emilyhopkins commented 3 years ago

https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source

napulen commented 3 years ago

The site won't be served until Pages is set up in the settings of the repo.

emilyhopkins commented 3 years ago

Yes, I thought that was the standard way to deploy GitHub pages sites? Is this the same as using GitHub actions? Where you just go Settings > Pages and then point to the branch you want for the site

napulen commented 3 years ago

The settings are the standard way to serve GitHub pages, assuming that the content of the branch is the HTML content.

Ich was referring to the automatic deployment using gh-actions for the cases where you need to build the website first, then serve the generated output in a different branch (e.g., build a static site in Flask, and serve the generated html on gh-pages; this can be scripted using gh-actions).

As GitHub already builds jekyll sites by default, this process is actually abstracted from us, so there is no need for GitHub actions. Having the jekyll project is enough for GitHub to figure it out and render the website. Essentially, they run the bundle exec jekyll build for us.

emilyhopkins commented 3 years ago

OK, sounds good! Thanks for clarifying!

napulen commented 3 years ago

The site is running on: https://ddmal.music.mcgill.ca/linkedmusic-website/

There are some issues with the urls of assets and static resources.