Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automation tools #1

Open
8 tasks done
hossainemruz opened this issue Nov 1, 2020 · 4 comments
Open
8 tasks done

Automation tools #1

hossainemruz opened this issue Nov 1, 2020 · 4 comments

Comments

@hossainemruz
Copy link
Member

hossainemruz commented Nov 1, 2020

We should add the following automation tools:

Shridhad referenced this issue in Shridhad/hugo-toha.github.io Mar 10, 2021
Make header linkable + fix bug
Shridhad referenced this issue in Shridhad/hugo-toha.github.io Mar 10, 2021
@myrust
Copy link

myrust commented Aug 17, 2021

Request to add support for cloudflare automated deployment!
https://pages.cloudflare.com/

@hossainemruz
Copy link
Member Author

Sure. I will try.

@davelevine
Copy link

davelevine commented Jan 25, 2022

@myrust / @hossainemruz - the request for support for Cloudflare Pages is a few months old now, but in case you're still looking to make use of it, I was able to get it working. Its assumed that you've already connected your repo to Cloudflare Pages, but if you haven't, the steps can be found here.

Steps for deploying the theme to Pages are below...

  • Open Cloudflare Pages and click Create Project
  • Select the repo and click Begin Setup
  • Give the project a name and make sure the Production Branch is set to Source
  • In the Build settings, select the Hugo framework preset. Leave the build command and build output directory as their defaults, which can be seen in the image below.
  • Deploy the theme.

Screen Shot 2022-02-06 at 4 50 51 PM

A few things to note...

  • Leave the existing repo automation tools in place. Once a change has been committed, the tools will still be needed to create the build and push it to the Main branch.
  • No need to disable GitHub Pages if its already enabled. I have mine enabled, but just made sure to remove my custom domain from it as I run the domain through Cloudflare Pages.
  • Cloudflare Pages will attempt to build every branch by default so both the source and main branches will be deployed. Both will build and deploy successfully, but the main (Preview) branch will not display anything (at least according to my deployment). The source (Production) branch deployment will deploy properly.

@hossainemruz
Copy link
Member Author

Thank you @davelevine. I haven't got chance to work on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants