diff --git a/docs/blog/posts/2024-08-21-creating-ghost-site-using-flex.md b/docs/blog/posts/2024-08-21-creating-ghost-site-using-flex.md
index 7cf6e53..3a806e8 100644
--- a/docs/blog/posts/2024-08-21-creating-ghost-site-using-flex.md
+++ b/docs/blog/posts/2024-08-21-creating-ghost-site-using-flex.md
@@ -11,17 +11,19 @@ categories:
   - Server
 ---
 
-# Creating a Ghost site with Openstack-Flex
+## Creating a Ghost site with Openstack-Flex
 
 Welcome! In this blog post we are going over using Openstack-Flex to deploy Ghost. If you havent used ghost before and would like more information about it please visit their website using the link  [here](https://ghost.org/)
 
-## Getting Started:
+<!-- more -->
 
-First you will need to set up your clouds.yaml file to be able to complete the next steps. More information about that can be found [here](https://docs.rackspacecloud.com/build-test-envs/#configure-openstack-client). 
+## Getting Started
 
-## Creating our Openstack-Flex Server
+First you will need to set up your clouds.yaml file to be able to complete the next steps. More information about that can be found [here](https://docs.rackspacecloud.com/build-test-envs/#configure-openstack-client).
 
-Fist we are going to create our Flex router. 
+### Creating our Openstack-Flex Server
+
+First we are going to create our Flex router.
 
 ``` shell
 openstack  --os-cloud {cloud_name} router create flex-router
@@ -54,7 +56,7 @@ Connect the subnet to our flex-router
 openstack --os-cloud {cloud_name} router add subnet flex-router flex-subnet
 ```
 
-Now we need to create our security group, this is the group which specify the network access rules. For our example now we are only going to allow SSH access. 
+Now we need to create our security group, this is the group which specify the network access rules. For our example we are only going to allow SSH access.
 
 ``` shell
 openstack --os-cloud {cloud_name} security group create flex-sg
@@ -64,7 +66,7 @@ openstack --os-cloud {cloud_name} security group create flex-sg
 openstack --os-cloud {cloud_name} security group rule create --ingress --remote-ip 0.0.0.0/0 --dst-port 22 --protocol tcp flex-sg
 ```
 
-Now we need to create our floating ip. 
+Now we need to create our floating ip.
 
 !!! note
 
@@ -79,16 +81,16 @@ Now we are going to create our Public and Private ssh keys so we can securely co
 ``` shell
 ssh-keygen
 ```
-This will prompt you store and name your private key. I did something like this /home/{username}/.ssh/flex-key. 
+This will prompt you store and name your private key. I did something like this /home/{username}/.ssh/flex-key.
 
 After that we will create our public key using the command below then we will assign it using the the openstack cli tools.
 
 ``` shell
-ssh-keygen -f ~/.ssh/flex-key -y > ~/.ssh/flex-key.pub 
+ssh-keygen -f ~/.ssh/flex-key -y > ~/.ssh/flex-key.pub
 openstack —os-cloud {cloud_name} keypair create --public-key ~/.ssh/flex-key.pub flex-key
 ```
 
-Now we create our server! This should include the flavor you'd like to use, the image, memory, network, key-name, and security group for this example. 
+Now we create our server! This should include the flavor you'd like to use, the image, memory, network, key-name, and security group for this example.
 
 ``` shell
  openstack --os-cloud {cloud_name} server create --flavor m1.medium --image Ubuntu-22.04 --boot-from-volume 40 --network flex-network --key-name flex-key --security-group flex-sg flex-server
@@ -101,15 +103,15 @@ openstack --os-cloud {cloud_name} port list
 openstack --os-cloud {cloud_name} floating ip set --port {port id} {floating-ip}
 ```
 
-SSH into your new Server! 
+SSH into your new Server!
 
 ``` shell
 ssh -i ~/.ssh/flex-key ubuntu@{floating-ip}
 ```
 
-# Deploying our Ghost website on our Openstack-Flex server
+## Deploying our Ghost website on our Openstack-Flex server
 
-Once we have created our Openstack-Flex Server we will want to make sure everything is up to date. 
+Once we have created our Openstack-Flex Server we will want to make sure everything is up to date.
 
 ``` shell
 sudo apt-get update && sudo apt-get upgrade -y
@@ -132,14 +134,14 @@ Start nginx
 sudo systemctl start nginx
 ```
 
-Next we install Mysql 
+Next we install Mysql
 
 ``` shell
 sudo apt install mysql-server
 sudo mysql_secure_installation
 ```
 
-Next we need to use mysql and create our wordpress database with our username and password. Please create your own personal username and password. 
+Next we need to use mysql and create our wordpress database with our username and password. Please create your own personal username and password.
 
 ``` shell
 sudo mysql
diff --git a/docs/blog/posts/2024-09-11-running-cloud-native-applications.md b/docs/blog/posts/2024-09-11-running-cloud-native-applications.md
new file mode 100644
index 0000000..619ae04
--- /dev/null
+++ b/docs/blog/posts/2024-09-11-running-cloud-native-applications.md
@@ -0,0 +1,68 @@
+---
+date: 2024-09-11
+title: Running an Open Infrastructure Native Application
+authors:
+  - cloudnull
+description: >
+  Running an Open Infrastructure Native Application
+categories:
+  - General
+  - Application
+  - Server
+---
+
+I recently decided I needed to run an application on OpenStack Flex to make things real. So naturally, I wrote an application from scratch that's more than just a boilerplate bucket of bolts. The gist of what I did over the weekend was to make a tool that harnesses the power of OpenStack with a Swift kick in the teeth.
+
+<!-- more -->
+
+##### [Say hello to Gisty](https://gisty.link)
+
+In the vast ocean of the internet, where attention spans are shorter than the lifecycle of a JavaScript framework, Gisty emerges, a simple yet essential open-source code/content-sharing platform. Created for those fleeting moments when you want to drop some wisdom (or chaos) into the void, Gisty lets users submit content, store it securely, and retrieve it later via a unique URL; I designed it to be hilariously that simple.  
+
+## The Good, the Simple, and the Hilarious
+
+At its core, Gisty is like that reliable friend who always remembers your most embarrassing stories, except it does this for the content you submit. Generated content is hashed; that hash is a unique and shareable link. The user experience is blissfully simple: users submit their content via a form or API, and Gisty returns a unique URL that can be revisited later; it works on both the CLI and within the browser. A neat feature of the application is the ability to have self-destructive content, which is great when sharing things that may be potentially sensitive or something that you only want to read once.
+
+![Gisty Open Infrastructure Diagram](assets/images/2024-09-11/gisty-opentools.png)
+
+Gisty is dark in its sense of humor and its GitHub-inspired theme, powered by Tailwind CSS. The sleek and responsive interface looks so good that you almost forget the site is just a bin for pasted content. Behind the scenes, the content is stored in OpenStack Swift, where it sits quietly, waiting to be rediscovered or forgotten.
+
+### Swift as You've Never Known It
+
+Gisty was written in Swift and uses the Vapor web framework. I built this application using Swift because of its clean API, type safety, lightning speed, I enjoy it, and it is funny to me that I wrote the code in Swift to store objects on Swift.
+
+* The Vapor web framework handles all the routing, from submitting content to dynamically retrieving it
+* OpenStack Swift handles the storage and metadata; yes, it's meta, do not overthink it
+* On the front end, I used HTML and Tailwind CSS; no JavaScript here.
+
+The application's storage lies in OpenStack Swift. Submitted content is hashed into unique identifiers (so no one will know you've submitted the same "Hello World" program 40 times, nor will it consume 40 objects). The consistent hashing ensures there are no duplicate uploads. Content is stored securely in Swift's object storage, meaning that, theoretically, it will live on forever, or at least until the server explodes. In the event of server destruction, you can count on the power of the sad toothpaste tube to brighten your day.
+
+![Gisty error example](assets/images/2024-09-11/gisty-sad.png)
+
+The application uses a toothpaste tube as the iconography because the backend is full of your pastes. When exploring or rendering content, you get a happy toothpaste tube. If you need to do better or if there's an error, you'll see a sad toothpaste tube. This sad toothpaste tube is not just a random choice of icon, it is a representation of the essence of failure: crumpled, exhausted, and a little disheveled. After all, nothing soothes the sting of a 500 error like a sad look of a disheveled tube of toothpaste.
+
+> I opted for dark site with some dark humor. This dark humor is not just a design choice; it is a way to make the user experience more engaging and less intimidating.
+
+### Rackspace OpenStack Flex?
+
+Rackspace OpenStack Flex gives the application scalability, allowing it to handle a growing number of user submissions. A fantastic feature of OpenStack, available in OpenStack Flex, is the ability to use application credentials.
+
+![Gisty uses application credentials in OpenStack](assets/images/2024-09-11/gisty-app-creds.jpg)
+
+Application credentials keep my account-level access separate from my application, which is incredible because I can rotate or revoke the credentials as I see fit. Rackspace's native support for OpenStack made integration seamless. By seamless, I mean the Containerized app spins up nicely in CoreOS.
+
+> Podman was used to containerize the entire application, because why have a stable local development environment when you can throw it into a container and pretend everything is okay? With Rackspace OpenStack Flex, deploying Gisty was as easy as setting the application credentials and running `systemctl start gisty.service`.
+
+A load balancer fronts the traffic for the application nodes, giving me the horizontal scale I need to support a growing number of users. An all-mighty Let's Encrypt certificate gives users some feel-good encryption. Every application node is stateless, meaning I can scale horizontally to my heart's extent. To put it another way, leaning into some marketing doublespeak, the application is "cloud native."
+
+![Gisty is built for OpenStack](assets/images/2024-09-11/gisty-openstack-powered.png)
+
+## FIN
+
+In conclusion, Gisty is everything you never thought you wanted in a paste-sharing platform: sleek, efficient, and always on the verge of an existential crisis. Whether you're submitting code snippets, random thoughts, or, more likely, debugging messages to yourself, Gisty is here for you. Deployed on Rackspace OpenStack Flex, Gisty has been designed to scale, survive your requests, and occasionally make you laugh. So, the next time you see a sad toothpaste tube, remember: it's not broken; it's just having a bad day, and in the weather, that can change anytime.
+
+So that's Gisty. The gist of this effort was to introduce you to an actual application running on the foundational environment of Rackspace's new OpenStack cloud. It gives me something tangible to tinker with. I have to write some code and share this blog post, and I'm excited about what's coming soon.
+
+![Gisty OpenStack Topology](assets/images/2024-09-11/gisty-topology.png)
+
+Stay tuned for more!
diff --git a/docs/blog/posts/assets/images/2024-09-11/gisty-app-creds.jpg b/docs/blog/posts/assets/images/2024-09-11/gisty-app-creds.jpg
new file mode 100644
index 0000000..1308ca8
Binary files /dev/null and b/docs/blog/posts/assets/images/2024-09-11/gisty-app-creds.jpg differ
diff --git a/docs/blog/posts/assets/images/2024-09-11/gisty-openstack-powered.png b/docs/blog/posts/assets/images/2024-09-11/gisty-openstack-powered.png
new file mode 100644
index 0000000..2fcdc9d
Binary files /dev/null and b/docs/blog/posts/assets/images/2024-09-11/gisty-openstack-powered.png differ
diff --git a/docs/blog/posts/assets/images/2024-09-11/gisty-opentools.png b/docs/blog/posts/assets/images/2024-09-11/gisty-opentools.png
new file mode 100644
index 0000000..d7ad304
Binary files /dev/null and b/docs/blog/posts/assets/images/2024-09-11/gisty-opentools.png differ
diff --git a/docs/blog/posts/assets/images/2024-09-11/gisty-sad.png b/docs/blog/posts/assets/images/2024-09-11/gisty-sad.png
new file mode 100644
index 0000000..2c715a7
Binary files /dev/null and b/docs/blog/posts/assets/images/2024-09-11/gisty-sad.png differ
diff --git a/docs/blog/posts/assets/images/2024-09-11/gisty-topology.png b/docs/blog/posts/assets/images/2024-09-11/gisty-topology.png
new file mode 100644
index 0000000..7e84f87
Binary files /dev/null and b/docs/blog/posts/assets/images/2024-09-11/gisty-topology.png differ