hack13/hack13-blog
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Centered post images

Browse source
This commit is contained in:
Timothy Rogers 2021-10-29 10:30:19 -04:00
parent 9897104230
commit 636e401f82
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
content/posts/2021-10-29-cloudflare-workers-and-pages.md
View file

@ -24,9 +24,9 @@ That said, their latest service they have released public called [Pages](https:/
## Pages A Free CI/CD Dream
So the big reason why I have migrated to Cloudflare Pages for my site, is because it is so much easier to work on my site, test changes before they go public. I am able to push my changes to my GitHub repo for my site, and it kicks off a job immediately to update the site. It also builds the other branches on the fly as well, but gives them a unique link that isn't mapped to the regular live link so you can see the development builds of your site beside your live site.
{{< rawhtml >}}<center>{{< /rawhtml >}}
![Screen Shot 2021-10-29 at 8.24.55 AM.png](/post-pics/2021/Screen_Shot_2021-10-29_at_8.24.55_AM.png)
{{< rawhtml >}}</center>{{< /rawhtml >}}
As you can see from the image above you can see how it pulls, builds, and generates a unique site link for each commit. So as you can see, it on the back-end remaps your domain to the deployment link of the latest build. All the previous build hang around as well, so if I mess up on a build I can click the dots next to the build I need to go back to and the site will immediately roll back to that version of the site.
So I know you might be asking why I don't just use GitHub's built in Pages service. Well there are a couple reasons, and there are two big ones. The first one is that Cloudflare Pages push your site to all their edge nodes, so no matter where in the world someone visits the site, it will be loaded from the closest Cloudflare edge node. The second big feature is the extra features of ability to have custom error pages, routes, and more to your site.
@ -34,9 +34,9 @@ So I know you might be asking why I don't just use GitHub's built in Pages servi
## Workers Saving Me Money
So as I stated earlier, I also have been hosting an API server for people to use that uses my key to check against the [LastFM API](https://last.fm/) to get their Now Playing data and able to use it inside of NeosVR. I have to parse it into something not JSON or XML so that it is more easy to parse the data in game. So I was using a PHP script, but looking at the Cloudflare Workers... I am able to allow 100,000 requests every 24 hours. I haven't gotten over 45% usage yet. But even when I do the pricing is very affordable and there is no cold starts. All I had to do was teach myself JavaScript... which only took a day.
{{< rawhtml >}}<center>{{< /rawhtml >}}
![Screen Shot 2021-10-29 at 9.19.44 AM.png](/post-pics/2021/Screen_Shot_2021-10-29_at_9.19.44_AM.png)
{{< rawhtml >}}</center>{{< /rawhtml >}}
The image above shows the weekly report of my workers usage data. You also see, I have setup a lastfm-legacy that maps overtop of the old link for the lastfm system some people are still pointing at but has been re-written on the back-end to JavaScript on a Worker so that it gives them time to update to the new one.
So long story short, I am very happy to be back and learning JavaScript and doing new things. I am working on a Discord Bot right now for CyberFurz a small project I operate. I will be writing up on that soon once I finish everything on that front. Anyways, thank you for reading!