more image optimization

Updated all pictures since hugo migration to webp from png
This commit is contained in:
Timothy Rogers 2022-04-17 11:40:21 -04:00
parent dfc923e4b1
commit a5cd35ceb2
10 changed files with 4 additions and 4 deletions

View file

@ -22,7 +22,7 @@ That said, their latest service they have released public called [Pages](https:/
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. 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 >}} {{< 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) ![Screen Shot 2021-10-29 at 8.24.55 AM.webp](/post-pics/2021/Screen_Shot_2021-10-29_at_8.24.55_AM.webp)
{{< rawhtml >}}</center>{{< /rawhtml >}} {{< 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. 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.
@ -32,7 +32,7 @@ So I know you might be asking why I don't just use GitHub's built in Pages servi
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. 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 >}} {{< 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) ![Screen Shot 2021-10-29 at 9.19.44 AM.webp](/post-pics/2021/Screen_Shot_2021-10-29_at_9.19.44_AM.webp)
{{< rawhtml >}}</center>{{< /rawhtml >}} {{< 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. 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.

View file

@ -28,8 +28,8 @@ I know not everyone likes the concept or ideal of doing it this way when we have
I recently purchased 2 NFTs to help fund a content creator I follow on YouTube and they have been very transparent throughout the whole process. I got two Vaxxed Doggos, and they have been putting out spreadsheet and updating with with how they been using their funds they have received on their content. I recently purchased 2 NFTs to help fund a content creator I follow on YouTube and they have been very transparent throughout the whole process. I got two Vaxxed Doggos, and they have been putting out spreadsheet and updating with with how they been using their funds they have received on their content.
{{< rawhtml >}}<center> {{< rawhtml >}}<center>
<img src="/post-pics/2022/136.png" width="350" height="350"/> <img src="/post-pics/2022/136.webp" width="350" height="350"/>
<img src="/post-pics/2022/470.png" width="350" height="350"/> <img src="/post-pics/2022/470.webp" width="350" height="350"/>
<br /> <br />
<i>Vaxxed Doggo 136 &amp; Vaxxed Doggo 470, currently owned by me</i> <i>Vaxxed Doggo 136 &amp; Vaxxed Doggo 470, currently owned by me</i>
<br /> <br /> <br /> <br />

Binary file not shown.

Before

Width:  |  Height:  |  Size: 181 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 53 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 65 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 530 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 37 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 458 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 31 KiB