diff --git a/src/main.rs b/src/main.rs index 4cff737..eedf086 100644 --- a/src/main.rs +++ b/src/main.rs @@ -92,6 +92,16 @@ fn main(req: Request) -> Result { .with_content_type(mime::TEXT_HTML_UTF_8) .with_body(include_str!("static_site/hosfe.lt/public/posts/edge/index.html"))) }, + "/posts/edge2/" => { + Ok(Response::from_status(StatusCode::OK) + .with_content_type(mime::TEXT_HTML_UTF_8) + .with_body(include_str!("static_site/hosfe.lt/public/posts/edge2/index.html"))) + }, + "/images/edge-post-2_certificate.png" => { + Ok(Response::from_status(StatusCode::OK) + .with_content_type(mime::IMAGE_PNG) + .with_body(include_bytes!("static_site/hosfe.lt/public/images/edge-post-2_certificate.png").as_slice())) + }, // Catch all other requests and return a 404. _ => { Ok(Response::from_status(StatusCode::NOT_FOUND) diff --git a/src/static_site/hosfe.lt/content/posts/edge.md b/src/static_site/hosfe.lt/content/posts/edge.md index 91daba6..f7fc2f8 100644 --- a/src/static_site/hosfe.lt/content/posts/edge.md +++ b/src/static_site/hosfe.lt/content/posts/edge.md @@ -5,7 +5,14 @@ draft: false toc: true images: tags: - - untagged + - blog + - Fastly + - setup + - tech + - dns + - http + - wasm + - rust --- # I'm Six Feet From The Edge and I'm Thinking... diff --git a/src/static_site/hosfe.lt/content/posts/edge2.md b/src/static_site/hosfe.lt/content/posts/edge2.md new file mode 100644 index 0000000..9e83915 --- /dev/null +++ b/src/static_site/hosfe.lt/content/posts/edge2.md @@ -0,0 +1,98 @@ +--- +title: "This Blog is on the Edge Part 2: The Journey Continues" +date: 2024-01-22T16:16:18-05:00 +draft: false +toc: true +images: +tags: + - blog + - Fastly + - setup + - tech + - dns + - http + - wasm + - rust +--- + +# Part 2: The Journey Continues + +This is part two of how I got my blog on the edge using Fastly's Compute network. In this part I'll go over DNS, certificate setup, and what I use to build and deploy the blog in more detail. + +{{< admonition type=note title="Note" >}} +This post will be pretty Fastly specific when it comes to DNS and managing the certificates +{{< /admonition >}} + +In case you missed it the [first part is here](https://hosfe.lt/posts/edge/). + +## It's Always DNS + +I will admit I am not an expert here and what I have works for me and I had to run through a few trail and error runs to get what I wanted working. + +With that out of the way the first thing to do is take your domain name and in the [Fastly Admin Portal](https://manage.fastly.com) on your compute service from part 1 add them to the `Domains` section (this is the exact URL users will input when they want to visit your site). + +Here I have both (hosfe.lt and www.hosfe.lt). In the Fastly world it is better to have a subdomain (`www` or the like, I am planning on using `ricky` in the near future). I'll explain why later. + +Once this is done move onto the `Hosts`, here is the specific host you want to use (this can be just your root level domain e.g. hosfe.lt) as it will be the one the certificate covers. Normally this would be your origin but since this site is completely on the edge we are just using it for certificate security at this point. + +## TLS + +Now to secure the site we need to use the `Secure` feature of the dashboard. Here we can generate certificates for our host and any subdomains (I used the wildcard domain since I'll probably be moving from the root to `ricky.hosfe.lt` in the future and adding more subdomains for experiements). If you can I would recommend doing your root plus whatever subdomains you want (or wildcard). + +This step will also required you to put in an `_acme-challenge` to verify you actually own your domain. I use Digital Ocean for my domain networking and throwing that `CNAME` in along with it's value was easy. The first certificate took about 10 minutes to verify and propagate after that they have been less than a minute. + +## DNS Part 2: There's Always a Part 2 + +Once, you have your TLS certificate setup you should be good to go! In order to take full advantage of the edge you need to use a subdomain. This is because root domains are not allows to have a `CNAME` entry for them and must point to an `A` or `AAAA` record. You _can_ use Compute with a root domain and I'll show you how to find that here. + +### Finding Your CNAME Reference for Subdomains + +After we have created our TLS under the secure tab we need to know _which_ type of certificate we created. Going into the `Secure` App and `TLS Management` area we can click to view the certificate to see if we have a `t` or `s` type. + +![Which certificate type is active](/images/edge-post-2_certificate.png) + +Once we know that we can give our subdomain a `CNAME` that Fastly will utilize over the whole edge network. If you need more help there's a lot more info on the [developer docs](https://docs.fastly.com/en/guides/working-with-cname-records-and-your-dns-provider#tls-enabled-hostnames) + +### Finding the IP Address for your A Record and Root Domain + +While we are here we can also give the root domain an IP address to hit if you are keen on using that. This won't take advantage of the whole edge at first so this is why I mentioned previously that it was better to use a subdomain. There's a lot more info [here](https://docs.fastly.com/en/guides/using-fastly-with-apex-domains#when-you-have-tls-configured). + +That's it, you should now have a working secured website that is completely on the Fastly Compute network! Honestly, it's more work than GeoCities was but given the flexibility I am exited for the [internet to get weird again](https://www.rollingstone.com/culture/culture-commentary/internet-future-about-to-get-weird-1234938403/). + +## Hugo + +In case you're wondering the static site generator I am currently using is [Hugo](https://gohugo.io). The Theme is [hermit-v2](https://themes.gohugo.io/themes/hermit-v2/). Realistically I wanted a simple yet customizable theme and went with the first I found. I can also change it out pretty easily. Top that with an incredibly simple build system (literally compiling the site by just `hugo`) and I was sold. + + +## How to Deploy and GitHub Actions + +Lastly, how I currently deploy the blog. You can see my [GitHub Actions YAML here](https://github.com/deg4uss3r/hosfe.lt/blob/main/.github/workflows/test.yml). The important part is that I split this in two stages. A test and check on each commit/PR and a deploy only on a tag. This helps me control when I actually push content to the blog. + +```yaml +deploy: + if: | + startsWith(github.ref, 'refs/tags/v') && needs.test.result == 'success' +``` + +I love that little `if` statement. It will only deploy if the test suite was successful on a tagged run. + +Further one thing I found confusing at first was I needed to use the Fastly `fastly/compute-actions@v5` action not just the `deploy` action as it still needs to compile and ship the WASM binary. After that it was pretty easy to get working, it will use the `fastly.toml` at the root of the project and off it goes just like doing it via the CLI (see [Part 1](https://hosfe.lt/posts/edge/) to set that up). + +{{< admonition type=danger title="WARNING" >}} +Don't forget to store your Fastly API token in GitHub Secrets so you don't expose it! +{{< /admonition >}} + +```yaml + env: + FASTLY_API_TOKEN: ${{ secrets.FASTLY_API_TOKEN }} +``` + +## What's next? + +First, there's some DNS changes I want to make which won't be too bad and shouldn't have an affect on the structure of the site. Moving from the root domain for the blog to `ricky.hosfe.lt` and making the root a landing page only. + +For the website I got some great suggestions and probably the first one will be compressing the included HTML text (and incorporated images) and shrinking the size of the WASM binary that gets uploaded (right now sitting at 1.78Mb). Though with the inline image I'm sure a little larger as of today. + +Next, I would like to add much more logging and statistics to understand traffic flow and be able to play with observability and what's possible with the compute platform (with the added benefit of knowing how little people have read the blog). + + Slowly but surely I'll get to those but I also want to sprinkle in writing on some topics I want to chat about. So see you soon and I hope this helps, enjoy! diff --git a/src/static_site/hosfe.lt/hugo.toml b/src/static_site/hosfe.lt/hugo.toml index 66fa471..59a0e97 100644 --- a/src/static_site/hosfe.lt/hugo.toml +++ b/src/static_site/hosfe.lt/hugo.toml @@ -5,7 +5,6 @@ defaultContentLanguageInSubdir = false theme = "hermit-v2" pygmentsCodefences = true -pygmentsUseClasses = true copyright = "2023" @@ -76,3 +75,5 @@ disableKinds = ["taxonomy", "term"] [markup.goldmark.renderer] unsafe= true +[markup.highlight] +style="dracula" diff --git a/src/static_site/hosfe.lt/assets/custom_css/custom.css b/src/static_site/hosfe.lt/public/custom_css/custom.css similarity index 100% rename from src/static_site/hosfe.lt/assets/custom_css/custom.css rename to src/static_site/hosfe.lt/public/custom_css/custom.css diff --git a/src/static_site/hosfe.lt/public/images/edge-post-2_certificate.png b/src/static_site/hosfe.lt/public/images/edge-post-2_certificate.png new file mode 100644 index 0000000..3396af0 Binary files /dev/null and b/src/static_site/hosfe.lt/public/images/edge-post-2_certificate.png differ diff --git a/src/static_site/hosfe.lt/public/index.xml b/src/static_site/hosfe.lt/public/index.xml index 53a4075..a688d12 100644 --- a/src/static_site/hosfe.lt/public/index.xml +++ b/src/static_site/hosfe.lt/public/index.xml @@ -7,8 +7,15 @@ Hugo -- gohugo.io en-us 2023 - Fri, 05 Jan 2024 09:18:47 -0500 + Mon, 22 Jan 2024 16:16:18 -0500 + + This Blog is on the Edge Part 2: The Journey Continues + https://hosfe.lt/posts/edge2/ + Mon, 22 Jan 2024 16:16:18 -0500 + https://hosfe.lt/posts/edge2/ + Part 2: The Journey Continues This is part two of how I got my blog on the edge using Fastly&rsquo;s Compute network. In this part I&rsquo;ll go over DNS, certificate setup, and what I use to build and deploy the blog in more detail. Note This post will be pretty Fastly specific when it comes to DNS and managing the certificates In case you missed it the first part is here. + It's 2024 and This Blog is Now On The Edge https://hosfe.lt/posts/edge/ diff --git a/src/static_site/hosfe.lt/public/posts/edge-post-2_certificate.png b/src/static_site/hosfe.lt/public/posts/edge-post-2_certificate.png new file mode 100644 index 0000000..3396af0 Binary files /dev/null and b/src/static_site/hosfe.lt/public/posts/edge-post-2_certificate.png differ diff --git a/src/static_site/hosfe.lt/public/posts/edge/index.html b/src/static_site/hosfe.lt/public/posts/edge/index.html index 24a988c..8b3a262 100644 --- a/src/static_site/hosfe.lt/public/posts/edge/index.html +++ b/src/static_site/hosfe.lt/public/posts/edge/index.html @@ -22,7 +22,7 @@ I am taking advantage of learning at my new job by utilizing Fastly’s Edge Compute service and deploying this blog from their edge network making this site 100% delivered from a WASM pre-compiled binary."> - + @@ -89,7 +89,7 @@

It's 2024 and This Blog is Now On The Edge

Ricky Hosfelt

-

untagged

+

blogFastlysetuptechdnshttpwasmrust

1733 Words – @@ -124,11 +124,11 @@

Some Warnings FirstThe Blog’s Code

The main focus of this section will be my main.rs Rust module (on GitHub). The source HTML is also in there but that is less interesting and I will briefly cover that later.

The main content is very simple just a large match statement based off of the incoming request’s path and then serving that in a response through pre-compiled HTML. essentially this boils down to very few lines of code:

-
match req.get_path() {
-  "/" => include_str!("../index.html"),
-  _ => include_str!("../404.html"),
-} 
-

Yes, astute readers will realize that every new page will need a new line to that match statement; however, it’s a small price to pay for this being incredibly simple. I could setup some glob matches if I hosted the pages on an external service (e.g. S3, Droplet, etc.). That’s something I’d like to explore on a future date but for now this is fast, convenient, and fits nicely into a simple enough workflow for a very casual website updater 😅.

+
match req.get_path() {
+  "/" => include_str!("../index.html"),
+  _ => include_str!("../404.html"),
+} 
+

Yes, astute readers will realize that every new page will need a new line to that match statement; however, it’s a small price to pay for this being incredibly simple. I could setup some glob matches if I hosted the pages on an external service (e.g. S3, Droplet, etc.). That’s something I’d like to explore on a future date but for now this is fast, convenient, and fits nicely into a simple enough workflow for a very casual website updater 😅.

A quick note on the include_str!() macro. If you’re not immediately familiar this is including the input file in the compiled binary. So while sacrificing binary size by including the text there’s no file system lookup or network hit required to serve each request. It also has the advantage that if that file does not exist the binary will not compile so I cannot serve you a file that does not exist (but I can leave out files that do exist).

Okay, But How Do You Get Started?

So that is all simple enough but getting started was a little bit confusing for me (I could not find a specific set of cohesive steps to get started) so I’ll walk through how I did it. Previous caveats apply here, this is information I cobbled together and not the best way but a way that works for me.

@@ -152,13 +152,13 @@

Okay, But How Do You Get Started?

After that I installed the Fastly CLI (or you can do everything from the web if you prefer but I like using CLIs so I do when I can). For me that was as simple as following the brew install fastly/tap/fastly command.

Next up we’ll test out a working CLI interface. I use 1Password’s CLI to help insert secrets without leaking them (read the install instructions here: 1Password CLI); however, you can do what you are most comfortable with (both security and tool-wise). The command I would recommend running first is:

-
~ fastly whoami --token $(op item get "$YOUR_FASTLY_ITEM_NAME" --fields $YOUR_API_TOKEN_FIELD_NAME)
+
~ fastly whoami --token $(op item get "$YOUR_FASTLY_ITEM_NAME" --fields $YOUR_API_TOKEN_FIELD_NAME)
 
If you get an output with your name and email you are good to go! Otherwise it would appear the account token you’ve generated isn’t working or you have a previous configuration somewhere that is messing with it. Reach out to the Fastly Developer Docs or the Contact the community for additional help.

 
Once you have a successful result from whoami you’re ready to push to your service! I would recommend following the Rust template repository by forking it and pushing a single simple page (e.g. one match arm with the catchall as well) with anything you want. Do so by calling the following inside the template repo:

-
~ fastly compute publish --token $YOUR_TOKEN --service-id $YOUR_SERVICE_ID
+
~ fastly compute publish --token $YOUR_TOKEN --service-id $YOUR_SERVICE_ID
 
Once that deploys you can check it via the Management portal, click on Compute > Your Service > Version Number > Then you should see “Test Domain” next to your domain.

 
As you get more complex or if you want to test the binary locally you can do so very easily just:

-
~ fastly compute serve
+
~ fastly compute serve
 

     
 		

+			
 			
diff --git a/src/static_site/hosfe.lt/public/posts/edge2/index.html b/src/static_site/hosfe.lt/public/posts/edge2/index.html
new file mode 100644
index 0000000..4638508
--- /dev/null
+++ b/src/static_site/hosfe.lt/public/posts/edge2/index.html
@@ -0,0 +1,207 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+This Blog is on the Edge Part 2: The Journey Continues
+
+	
+
+	
+	

+		
+	

+
+
+	

+			

+				
Jan 22, 2024

+				
This Blog is on the Edge Part 2: The Journey Continues

+			

+			
Ricky Hosfelt

+
blogFastlysetuptechdnshttpwasmrust

+
1060 Words
+    –
+    
+    
+    
+    4 Minutes, 49 Seconds

+
2024-01-22 16:16 -0500

+			

+			

+				
Part 2: The Journey Continues

+
This is part two of how I got my blog on the edge using Fastly’s Compute network. In this part I’ll go over DNS, certificate setup, and what I use to build and deploy the blog in more detail.

+
+    
+
In case you missed it the first part is here.

+
It’s Always DNS

+
I will admit I am not an expert here and what I have works for me and I had to run through a few trail and error runs to get what I wanted working.

+
With that out of the way the first thing to do is take your domain name and in the Fastly Admin Portal on your compute service from part 1 add them to the  Domains section (this is the exact URL users will input when they want to visit your site).

+
Here I have both (hosfe.lt and www.hosfe.lt). In the Fastly world it is better to have a subdomain (www or the like, I am planning on using ricky in the near future). I’ll explain why later.

+
Once this is done move onto the Hosts, here is the specific host you want to use (this can be just your root level domain e.g. hosfe.lt) as it will be the one the certificate covers. Normally this would be your origin but since this site is completely on the edge we are just using it for certificate security at this point.

+
TLS

+
Now to secure the site we need to use the Secure feature of the dashboard. Here we can generate certificates for our host and any subdomains (I used the wildcard domain since I’ll probably be moving from the root to ricky.hosfe.lt in the future and adding more subdomains for experiements). If you can I would recommend doing your root plus whatever subdomains you want (or wildcard).

+
This step will also required you to put in an _acme-challenge to verify you actually own your domain. I use Digital Ocean for my domain networking and throwing that CNAME in along with it’s value was easy. The first certificate took about 10 minutes to verify and propagate after that they have been less than a minute.

+
DNS Part 2: There’s Always a Part 2

+
Once, you have your TLS certificate setup you should be good to go! In order to take full advantage of the edge you need to use a subdomain. This is because root domains are not allows to have a CNAME entry for them and must point to an A or AAAA record. You can use Compute with a root domain and I’ll show you how to find that here.

+
Finding Your CNAME Reference for Subdomains

+
After we have created our TLS under the secure tab we need to know which type of certificate we created. Going into the Secure App and TLS Management area we can click to view the certificate to see if we have a t or s type.

+
Which certificate type is active

+
Once we know that we can give our subdomain a CNAME that Fastly will utilize over the whole edge network. If you need more help there’s a lot more info on the developer docs

+
Finding the IP Address for your A Record and Root Domain

+
While we are here we can also give the root domain an IP address to hit if you are keen on using that. This won’t take advantage of the whole edge at first so this is why I mentioned previously that it was better to use a subdomain. There’s a lot more info here.

+
That’s it, you should now have a working secured website that is completely on the Fastly Compute network! Honestly, it’s more work than GeoCities was but given the flexibility I am exited for the internet to get weird again.

+
Hugo

+
In case you’re wondering the static site generator I am currently using is Hugo. The Theme is hermit-v2. Realistically I wanted a simple yet customizable theme and went with the first I found. I can also change it out pretty easily. Top that with an incredibly simple build system (literally compiling the site by just hugo) and I was sold.

+
How to Deploy and GitHub Actions

+
Lastly, how I currently deploy the blog. You can see my GitHub Actions YAML here. The important part is that I split this in two stages. A test and check on each commit/PR and a deploy only on a tag. This helps me control when I actually push content to the blog.

+
deploy:
+    if: |
+      startsWith(github.ref, 'refs/tags/v') && needs.test.result == 'success'      
+
I love that little if statement. It will only deploy if the test suite was successful on a tagged run.

+
Further one thing I found confusing at first was I needed to use the Fastly fastly/compute-actions@v5 action not just the deploy action as it still needs to compile and ship the WASM binary. After that it was pretty easy to get working, it will use the fastly.toml at the root of the project and off it goes just like doing it via the CLI (see Part 1 to set that up).

+
+    
+
      env:
+        FASTLY_API_TOKEN: ${{ secrets.FASTLY_API_TOKEN }}
+
What’s next?

+
First, there’s some DNS changes I want to make which won’t be too bad and shouldn’t have an affect on the structure of the site. Moving from the root domain for the blog to ricky.hosfe.lt and making the root a landing page only.

+
For the website I got some great suggestions and probably the first one will be compressing the included HTML text (and incorporated images) and shrinking the size of the WASM binary that gets uploaded (right now sitting at 1.78Mb). Though with the inline image I’m sure a little larger as of today.

+
Next, I would like to add much more logging and statistics to understand traffic flow and be able to play with observability and what’s possible with the compute platform (with the added benefit of knowing how little people have read the blog).

+
Slowly but surely I’ll get to those but I also want to sprinkle in writing on some topics I want to chat about. So see you soon and I hope this helps, enjoy!

+
+			

+
+

+	
See Also

+	
+

+
+		

+		
+		

+			
+		

+		

+

+	

+
+
+
+
+
+
diff --git a/src/static_site/hosfe.lt/public/posts/index.html b/src/static_site/hosfe.lt/public/posts/index.html
index 9bde325..d5c76a5 100644
--- a/src/static_site/hosfe.lt/public/posts/index.html
+++ b/src/static_site/hosfe.lt/public/posts/index.html
@@ -80,6 +80,12 @@ 
Posts

 		

 			
2024

+

This is part two of how I got my blog on the edge using Fastly’s Compute network. In this part I’ll go over DNS, certificate setup, and what I use to build and deploy the blog in more detail.

+ + +

In case you missed it the first part is here.

+

It’s Always DNS

+

I will admit I am not an expert here and what I have works for me and I had to run through a few trail and error runs to get what I wanted working.

+

With that out of the way the first thing to do is take your domain name and in the Fastly Admin Portal on your compute service from part 1 add them to the Domains section (this is the exact URL users will input when they want to visit your site).

+

Here I have both (hosfe.lt and www.hosfe.lt). In the Fastly world it is better to have a subdomain (www or the like, I am planning on using ricky in the near future). I’ll explain why later.

+

Once this is done move onto the Hosts, here is the specific host you want to use (this can be just your root level domain e.g. hosfe.lt) as it will be the one the certificate covers. Normally this would be your origin but since this site is completely on the edge we are just using it for certificate security at this point.

+

TLS

+

Now to secure the site we need to use the Secure feature of the dashboard. Here we can generate certificates for our host and any subdomains (I used the wildcard domain since I’ll probably be moving from the root to ricky.hosfe.lt in the future and adding more subdomains for experiements). If you can I would recommend doing your root plus whatever subdomains you want (or wildcard).

+

This step will also required you to put in an _acme-challenge to verify you actually own your domain. I use Digital Ocean for my domain networking and throwing that CNAME in along with it’s value was easy. The first certificate took about 10 minutes to verify and propagate after that they have been less than a minute.

+

DNS Part 2: There’s Always a Part 2

+

Once, you have your TLS certificate setup you should be good to go! In order to take full advantage of the edge you need to use a subdomain. This is because root domains are not allows to have a CNAME entry for them and must point to an A or AAAA record. You can use Compute with a root domain and I’ll show you how to find that here.

+

Finding Your CNAME Reference for Subdomains

+

After we have created our TLS under the secure tab we need to know which type of certificate we created. Going into the Secure App and TLS Management area we can click to view the certificate to see if we have a t or s type.

+

Which certificate type is active

+

Once we know that we can give our subdomain a CNAME that Fastly will utilize over the whole edge network. If you need more help there’s a lot more info on the developer docs

+

Finding the IP Address for your A Record and Root Domain

+

While we are here we can also give the root domain an IP address to hit if you are keen on using that. This won’t take advantage of the whole edge at first so this is why I mentioned previously that it was better to use a subdomain. There’s a lot more info here.

+

That’s it, you should now have a working secured website that is completely on the Fastly Compute network! Honestly, it’s more work than GeoCities was but given the flexibility I am exited for the internet to get weird again.

+

Hugo

+

In case you’re wondering the static site generator I am currently using is Hugo. The Theme is hermit-v2. Realistically I wanted a simple yet customizable theme and went with the first I found. I can also change it out pretty easily. Top that with an incredibly simple build system (literally compiling the site by just hugo) and I was sold.

+

How to Deploy and GitHub Actions

+

Lastly, how I currently deploy the blog. You can see my GitHub Actions YAML here. The important part is that I split this in two stages. A test and check on each commit/PR and a deploy only on a tag. This helps me control when I actually push content to the blog.

+
deploy:
+    if: |
+      startsWith(github.ref, 'refs/tags/v') && needs.test.result == 'success'      
+

I love that little if statement. It will only deploy if the test suite was successful on a tagged run.

+

Further one thing I found confusing at first was I needed to use the Fastly fastly/compute-actions@v5 action not just the deploy action as it still needs to compile and ship the WASM binary. After that it was pretty easy to get working, it will use the fastly.toml at the root of the project and off it goes just like doing it via the CLI (see Part 1 to set that up).

+ + +
      env:
+        FASTLY_API_TOKEN: ${{ secrets.FASTLY_API_TOKEN }}
+

What’s next?

+

First, there’s some DNS changes I want to make which won’t be too bad and shouldn’t have an affect on the structure of the site. Moving from the root domain for the blog to ricky.hosfe.lt and making the root a landing page only.

+

For the website I got some great suggestions and probably the first one will be compressing the included HTML text (and incorporated images) and shrinking the size of the WASM binary that gets uploaded (right now sitting at 1.78Mb). Though with the inline image I’m sure a little larger as of today.

+

Next, I would like to add much more logging and statistics to understand traffic flow and be able to play with observability and what’s possible with the compute platform (with the added benefit of knowing how little people have read the blog).

+

Slowly but surely I’ll get to those but I also want to sprinkle in writing on some topics I want to chat about. So see you soon and I hope this helps, enjoy!

+]]> + + It's 2024 and This Blog is Now On The Edge https://hosfe.lt/posts/edge/ @@ -42,11 +103,11 @@ I am taking advantage of learning at my new job by utilizing Fastly&rsquo;s

The Blog’s Code

The main focus of this section will be my main.rs Rust module (on GitHub). The source HTML is also in there but that is less interesting and I will briefly cover that later.

The main content is very simple just a large match statement based off of the incoming request’s path and then serving that in a response through pre-compiled HTML. essentially this boils down to very few lines of code:

-
match req.get_path() {
-  "/" => include_str!("../index.html"),
-  _ => include_str!("../404.html"),
-} 
-

Yes, astute readers will realize that every new page will need a new line to that match statement; however, it’s a small price to pay for this being incredibly simple. I could setup some glob matches if I hosted the pages on an external service (e.g. S3, Droplet, etc.). That’s something I’d like to explore on a future date but for now this is fast, convenient, and fits nicely into a simple enough workflow for a very casual website updater 😅.

+
match req.get_path() {
+  "/" => include_str!("../index.html"),
+  _ => include_str!("../404.html"),
+} 
+

Yes, astute readers will realize that every new page will need a new line to that match statement; however, it’s a small price to pay for this being incredibly simple. I could setup some glob matches if I hosted the pages on an external service (e.g. S3, Droplet, etc.). That’s something I’d like to explore on a future date but for now this is fast, convenient, and fits nicely into a simple enough workflow for a very casual website updater 😅.

A quick note on the include_str!() macro. If you’re not immediately familiar this is including the input file in the compiled binary. So while sacrificing binary size by including the text there’s no file system lookup or network hit required to serve each request. It also has the advantage that if that file does not exist the binary will not compile so I cannot serve you a file that does not exist (but I can leave out files that do exist).

Okay, But How Do You Get Started?

So that is all simple enough but getting started was a little bit confusing for me (I could not find a specific set of cohesive steps to get started) so I’ll walk through how I did it. Previous caveats apply here, this is information I cobbled together and not the best way but a way that works for me.

@@ -70,13 +131,13 @@ I am taking advantage of learning at my new job by utilizing Fastly&rsquo;s

After that I installed the Fastly CLI (or you can do everything from the web if you prefer but I like using CLIs so I do when I can). For me that was as simple as following the brew install fastly/tap/fastly command.

Next up we’ll test out a working CLI interface. I use 1Password’s CLI to help insert secrets without leaking them (read the install instructions here: 1Password CLI); however, you can do what you are most comfortable with (both security and tool-wise). The command I would recommend running first is:

-
~ fastly whoami --token $(op item get "$YOUR_FASTLY_ITEM_NAME" --fields $YOUR_API_TOKEN_FIELD_NAME)
+
~ fastly whoami --token $(op item get "$YOUR_FASTLY_ITEM_NAME" --fields $YOUR_API_TOKEN_FIELD_NAME)
 
If you get an output with your name and email you are good to go! Otherwise it would appear the account token you’ve generated isn’t working or you have a previous configuration somewhere that is messing with it. Reach out to the Fastly Developer Docs or the Contact the community for additional help.

 
Once you have a successful result from whoami you’re ready to push to your service! I would recommend following the Rust template repository by forking it and pushing a single simple page (e.g. one match arm with the catchall as well) with anything you want. Do so by calling the following inside the template repo:

-
~ fastly compute publish --token $YOUR_TOKEN --service-id $YOUR_SERVICE_ID
+
~ fastly compute publish --token $YOUR_TOKEN --service-id $YOUR_SERVICE_ID
 
Once that deploys you can check it via the Management portal, click on Compute > Your Service > Version Number > Then you should see “Test Domain” next to your domain.

 
As you get more complex or if you want to test the binary locally you can do so very easily just:

-
~ fastly compute serve
+
~ fastly compute serve