Infrastructure/tylerperkins.xyz
2
1
Fork 0
Code Issues Pull Requests Packages Activity

Update style and first post
All checks were successful
continuous-integration/drone/push Build is passing
Details

Browse Source
This commit is contained in:
Tyler Perkins 2023-09-11 22:45:24 -04:00
parent 786d8b3fcc
commit dfa985812f
4 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
content/posts/first-post.md
View File

@ -4,17 +4,15 @@ date: 2023-09-11T21:30:41-04:00
draft: false
---
# First Post
This is my first post from the rewrite! I decided to rewrite my website in [Hugo](https://gohugo.io) this time instead of PHP. The real innovation here is the new tech stack underpinning the process of hosting this thing.
So previously, I had no clue about "real" server hosting (like what actual companies do). But now that I have some experience under my belt in both my professional environment and in my hobby hosting, I now know a bit more about how to host in a more durable manner. Over engineering? Probably. But that's where the fun lies!
## New Tech Stack
The new tech stack this time around is a replicated S3 bucket (hosted using [Minio](https://min.io)) that is hosted in two separate sites, and synced together every 10 mins is hosting the content for this website. Then an nginx reverse proxy is doing some basic security and routing rules, then forwarding it to you as you see it currently. Pretty sweet!
The new tech stack this time around is a replicated S3 bucket ( hosted using [Minio](https://min.io) ) that is hosted in two separate sites, and synced together every 10 mins is hosting the content for this website. Then an nginx reverse proxy is doing some basic security and routing rules, then forwarding it to you as you see it currently. Pretty sweet!
The real win for me comes from a great simplification of the deployment process, though. With hugo, I can build the static website, then with my self hosted CI/CD runner ([Drone](https://drone.io), my self hosted instance is [here](https://drone.clortox.com)) I can auto build the site then deploy it, and only change the state in the bucket! How awesome is that!
The real win for me comes from a great simplification of the deployment process, though. With hugo, I can build the static website, then with my self hosted CI/CD runner ( [Drone](https://drone.io), my self hosted instance is [here](https://drone.clortox.com) ) I can auto build the site then deploy it, and only change the state in the bucket! How awesome is that!
![](https://s3.clortox.com/static-assets/img/mermaid-diagram-2023-09-11-214406.png)

1
layouts/_default/_markup/render-image.html Normal file
View File

@ -0,0 +1 @@
<center><img src="{{ .Destination }}" title="{{ with .Title }}{{ . }} {{ else }}{{ .Text }}{{ end }}" alt="{{ .Text }}" /></center>

1
layouts/_default/_markup/render-link.html Normal file
View File

@ -0,0 +1 @@
<a href="{{ .Destination }}" title="{{ .Title }}" data-value="{{ .Text | safeHTML }}" class="scramble">{{ .Text | safeHTML }}</a>

9
static/css/styles.css
View File

@ -185,7 +185,7 @@ html {
object-fit: contain;
}
article a {
article > a {
text-decoration: none;
display: flex;
padding: 50px;
@ -196,12 +196,15 @@ article a {
transition: background 200ms linear;
}
article a:hover {
article > a:hover {
background: black;
}
.post {
margin: 10px;
margin-right: 10vw;
margin-left: 10vw;
margin-top: 3vh;
margin-bottom: 1vh;
}
img {