TTY

                                                                 
 ________ ________   ________ ________   _____      _____ 
|\        \      /| |\        \      /| |\    \    /    /|
| \___     \ ___/ | | \___     \ ___/ | | \    \  /    / |
\ |   |\    \   | / \ |   |\    \   | / |  \____\/    /  /
 \|___| \    \__|/   \|___| \    \__|/   \ |    /    /  / 
      \  \    \           \  \    \       \|___/    /  /  
       \  \    \           \  \    \          /    /  /   
        \  \____\           \  \____\        /____/  /    
         \ |    |            \ |    |        |    | /     
          \|____|             \|____|        |____|/

Links

Categories

Posts

Linux Bottom Half

The information in this post may not be up-to-date, and it is primarily for my learning purposes. Please feel free to email me with any incorrect information.

Analyzing Homepage Traffic

I’ve recently switched from using Lamdba@Edge to Cloudfront Functions as it was a better option for my use case. I’ve covered it briefly in this post.

Serial Communication via Software

Continuing from the last project (7-segment display device driver), I wanted to expand the project to use hardware interrupts. So, this project was aimed towards implementing a software approach to serial communication that is able to handle both transmission and receival (TX/RX).

Using Cloudfront Functions instead of Lambda

Recently, I had to upgrade the Node.js version on my AWS Lambda function. The function was a pretty simple URI parser which was needed for my homepage to add/remove file extensions to the requested URL. For example, when a user first visits thinkty.net/, they probably want to see my homepage which is actually thinkty.net/index.html and not the home directory. So, for those cases, a Lambda function (Lambda@Edge) would intervene and update the URI accordingly to ensure that the user sees what they want. To learn more about homepage setup using AWS tools, checkout my other post.