search

coopdevs / coopdevs-old-web

coopdevs.org content
http://coopdevs.org
2 stars 10 forks source link

Automate build & deploy #36

Closed sauloperez closed 4 years ago

sauloperez commented 5 years ago

This stems from https://github.com/coopdevs/coopdevs.github.io/pull/31#issuecomment-446232057.

As we want to have people other than devs to write on our site, it's important to have the build and deploy happen elsewhere, not in people's machines. While we're able to setup the project on our dev machines, others don't.

Also, it's less error-prone to trust these steps to a 3rd party service/server so no conflicts with dependencies or problems with the dev machine stop you from deploying.

sauloperez commented 5 years ago

Gitlab pages is an option here. Apparently, they support any Jekyll plugin and the deploy uses their CI pipelines. Reference: https://www.scivision.co/gitlab-pages-vs-github-pages/

sauloperez commented 5 years ago

I'd do this as soon as we do a new iteration on the website's design and content. I would really glad to use my brain for other things other than having to deploy when PRs get merged. I prefer a computer to do it for me.

I worked already with Gitlab Pages at https://gitlab.com/sauloperez/municipalistes_republicans and it was a smooth experience. It works out of the box with their CI/CD templates :ok_hand:

enricostano commented 5 years ago

GitLab o ke ase?

sauloperez commented 4 years ago

Done in https://github.com/coopdevs/coopdevs.github.io/pull/70. We found a quicker solution that didn't require moving the repo.