I’ve been working out the steps for making this happen in Azure using my primary Jekyll blog.
I needed to break it down into a few key steps:
- Infrastructure
- setting up Azure, Azure Front Door, a domain and routing traffic
- Hugo
- setting up Hugo first in Linux, but then testing on another computer in WSL
- This meant having a proper GIT Repo in Forgejo
- CICD
- Getting my GIT provider actions (Forgejo/Gitea) working with the az CLI
- Creating an SP that could do non-interactive logins to expire the cache in Azure Front Door
So far this has been a fun experience.
My further refinements might involve:
- more narrowly scoping the SPs permissions
- looking at making a “test” site, perhaps something like “test.xxx.xxx” or using a different bucket (blob container) for a “preview” site
- Hugo plugins and refinement - all I really did was pick a theme
Lastly, I’ll evaluate if this is the right path to migrate Freshbrewed.science. Thats a 7Gb (compressed) GIT repo today and I might just archive for history and start fresh with Hugo.
I need to see some costing of Azure to compare with AWS today (S3 and CloudFront is really quite cheap).