Using Cloudflare for deployments of the guide

[mpizenberg]

No description provided.

[mpizenberg]

This Cloudflare setup seems to be working fine. I have created a pubgrub-rs-guide page on my cloudflare account and this action is configured to automatically publish to that project. Commits from the main branch will be published to production at https://pubgrub-rs-guide.pages.dev while commits on other branches will trigger preview builds with a dedicated subdomain for each preview build. For example, the latest commit before this comment was pushed to https://42264cb3.pubgrub-rs-guide.pages.dev/

This solves issue #10

Eventually, it would be nice to have the website owned by not me, but this is already an improvement compared to our previous netlify setup.

Using github pages would also be an option, but currently there are two downsides coming with it.

1. This forces repo bloat, by adding the build artifacts to one branch of the repo. Every commit published increasing the bloat. Can be mitigated by using an orphan branch and overwriting its only commit.
2. I'm not aware of a convenient way to have branch previews, only 1 publication is visible at any time.

[mpizenberg]

Actually, it seems that building github pages via actions artifacts instead of a branch is currently possible as a public beta feature https://github.com/actions/upload-pages-artifact. So that solves point (1) regarding repo bloat. When there is a solution to branch preview builds (2) I guess we can use github pages instead of cloudfare pages for more convenient access control from pubgrub-rs org.