diff --git a/content/about.md b/content/about.md index a77ad70..9199baf 100644 --- a/content/about.md +++ b/content/about.md @@ -1,7 +1,10 @@ +++ +type = misc + title = 'About' date = 2024-10-24T23:17:52+03:00 draft = false +bio = true +++ # About me diff --git a/content/posts/setup_p1.md b/content/posts/setup_p1.md index 0d1e924..bd21267 100644 --- a/content/posts/setup_p1.md +++ b/content/posts/setup_p1.md @@ -22,7 +22,7 @@ made a small change to the page, I had to manually rebuild it, then upload the updated version to my server and put it in the web directory. This is a cumbersome process. The whole point of using hugo is to *focus on the -writing*, so having to rebuild and reupload for every typo is... not great. I +writing*, so having to zip and reupload for every typo is... not great. I wanted to be able to do a simple `git push`, and not worry about the rest. The previous "manual" approach also depends on me having already installed all @@ -116,17 +116,18 @@ with each other. Usually, on a server, each application *isn't* totally separate from each other - for my own usecase, I want my git server (e.g. gogs) to automatically build and update my website whenever I push to its git repository. That means my git -server and web server can't be *totally* separate, there's some amount of relation. -Pods can help with this. +server and web server can't be *totally* separate, there's some amount of +relation. Pods can help with this. Pods allow you to create a "pod" containing several containers, sharing resources with each other, etc. For example, I could run a pod with nginx and gogs running -in seperate containers - then, the nginx server could act as a reverse proxy based -on host name, showing the web page on emin.software, and the git server on +in seperate containers - then, the nginx server could act as a reverse proxy +based on host name, showing the web page on emin.software, and the git server on git.emin.software. Nginx redirects to gogs which only binds to *the pod's localhost address*, so only nginx can reach it. Likewise, a database server can be added to the pod only for the git server to use, so that it can't be reached -from the outside the pod - and it is logically grouped along with the rest of the pod. +from the outside the pod - and it is logically grouped along with the rest of +the pod. -On top of this, pods can be built purely from a kubernetes-compatible configuration -file, so setting them up is relatively easy. +On top of this, pods can be built purely from a kubernetes-compatible +configuration file, so setting them up is relatively easy. diff --git a/public/404.html b/public/404.html index 48f286a..384fadb 100644 --- a/public/404.html +++ b/public/404.html @@ -1,5 +1,5 @@ - + @@ -43,7 +43,7 @@ - + @@ -72,7 +72,7 @@
- + haxala1r diff --git a/public/about/index.html b/public/about/index.html index 7911d6f..7c526c9 100644 --- a/public/about/index.html +++ b/public/about/index.html @@ -1,5 +1,5 @@ - + @@ -43,7 +43,7 @@ - + - + haxala1r diff --git a/public/categories/index.xml b/public/categories/index.xml index 4523662..5ca26e5 100644 --- a/public/categories/index.xml +++ b/public/categories/index.xml @@ -2,10 +2,10 @@ Categories on haxala1r - https://emin.software/categories/ + http://localhost:1313/categories/ Recent content in Categories on haxala1r Hugo en-us - + diff --git a/public/index.html b/public/index.html index fc15a05..05d5557 100644 --- a/public/index.html +++ b/public/index.html @@ -1,5 +1,5 @@ - + @@ -43,7 +43,7 @@ - + @@ -72,7 +72,7 @@
- + haxala1r diff --git a/public/index.xml b/public/index.xml index fa23507..5d1bbf7 100644 --- a/public/index.xml +++ b/public/index.xml @@ -2,24 +2,24 @@ haxala1r - https://emin.software/ + http://localhost:1313/ Recent content on haxala1r Hugo en-us Fri, 25 Oct 2024 23:11:17 +0300 - + My Setup - p1 - https://emin.software/posts/setup_p1/ + http://localhost:1313/posts/setup_p1/ Fri, 25 Oct 2024 23:11:17 +0300 - https://emin.software/posts/setup_p1/ + http://localhost:1313/posts/setup_p1/ My Setup In this ‘series’ I will be walking you through my process of how I host everything on this server. I’m currently running, on top of my blog, a gogs instance. When first creating this website, I just had my blog. I generated this blog using hugo: a static site generator. Hugo allowed me to focus on writing whatever I wanted in Markdown format, it would take care of converting my writing into HTML and CSS. About - https://emin.software/about/ + http://localhost:1313/about/ Thu, 24 Oct 2024 23:17:52 +0300 - https://emin.software/about/ + http://localhost:1313/about/ About me Hi, I’m Emin! I am a second year Computer Engineering student at Izmir University of Economics. I like all things programming and computers. I mostly do systems programming - I feel most at home when I use C++ or C, though I’ve used Rust, Java and many other languages to varying degrees. I also had a phase when I was really into Common Lisp. Seriously, using a language with true macros is an entirely different experience. diff --git a/public/posts/index.html b/public/posts/index.html index 003659c..2c0a41a 100644 --- a/public/posts/index.html +++ b/public/posts/index.html @@ -1,5 +1,5 @@ - + @@ -43,7 +43,7 @@ - + @@ -72,7 +72,7 @@
- + haxala1r diff --git a/public/posts/index.xml b/public/posts/index.xml index 4a1a6f9..d2defd3 100644 --- a/public/posts/index.xml +++ b/public/posts/index.xml @@ -2,17 +2,17 @@ Blog on haxala1r - https://emin.software/posts/ + http://localhost:1313/posts/ Recent content in Blog on haxala1r Hugo en-us Fri, 25 Oct 2024 23:11:17 +0300 - + My Setup - p1 - https://emin.software/posts/setup_p1/ + http://localhost:1313/posts/setup_p1/ Fri, 25 Oct 2024 23:11:17 +0300 - https://emin.software/posts/setup_p1/ + http://localhost:1313/posts/setup_p1/ My Setup In this ‘series’ I will be walking you through my process of how I host everything on this server. I’m currently running, on top of my blog, a gogs instance. When first creating this website, I just had my blog. I generated this blog using hugo: a static site generator. Hugo allowed me to focus on writing whatever I wanted in Markdown format, it would take care of converting my writing into HTML and CSS. diff --git a/public/posts/setup_p1/index.html b/public/posts/setup_p1/index.html index 85b763f..3204480 100644 --- a/public/posts/setup_p1/index.html +++ b/public/posts/setup_p1/index.html @@ -1,5 +1,5 @@ - + @@ -43,7 +43,7 @@ - + - + haxala1r @@ -178,7 +178,7 @@ converting my writing into HTML and CSS.

made a small change to the page, I had to manually rebuild it, then upload the updated version to my server and put it in the web directory.

This is a cumbersome process. The whole point of using hugo is to focus on the -writing, so having to rebuild and reupload for every typo is… not great. I +writing, so having to zip and reupload for every typo is… not great. I wanted to be able to do a simple git push, and not worry about the rest.

The previous “manual” approach also depends on me having already installed all necessary software. If you have a dedicated server that you’re running yourself, @@ -255,19 +255,20 @@ with each other.

  • for my own usecase, I want my git server (e.g. gogs) to automatically build and update my website whenever I push to its git repository. That means my git -server and web server can’t be totally separate, there’s some amount of relation. -Pods can help with this.
    • +server and web server can’t be totally separate, there’s some amount of +relation. Pods can help with this.

Pods allow you to create a “pod” containing several containers, sharing resources with each other, etc. For example, I could run a pod with nginx and gogs running -in seperate containers - then, the nginx server could act as a reverse proxy based -on host name, showing the web page on emin.software, and the git server on +in seperate containers - then, the nginx server could act as a reverse proxy +based on host name, showing the web page on emin.software, and the git server on git.emin.software. Nginx redirects to gogs which only binds to the pod’s localhost address, so only nginx can reach it. Likewise, a database server can be added to the pod only for the git server to use, so that it can’t be reached -from the outside the pod - and it is logically grouped along with the rest of the pod.

-

On top of this, pods can be built purely from a kubernetes-compatible configuration -file, so setting them up is relatively easy.

+from the outside the pod - and it is logically grouped along with the rest of +the pod.

+

On top of this, pods can be built purely from a kubernetes-compatible +configuration file, so setting them up is relatively easy.

 diff --git a/public/sitemap.xml b/public/sitemap.xml index 4d22c30..8be433a 100644 --- a/public/sitemap.xml +++ b/public/sitemap.xml @@ -2,20 +2,20 @@ - https://emin.software/posts/ + http://localhost:1313/posts/ 2024-10-28T23:41:06+03:00 - https://emin.software/ + http://localhost:1313/ 2024-10-28T23:41:06+03:00 - https://emin.software/posts/setup_p1/ + http://localhost:1313/posts/setup_p1/ 2024-10-25T23:11:17+03:00 - https://emin.software/about/ + http://localhost:1313/about/ 2024-10-24T23:17:52+03:00 - https://emin.software/categories/ + http://localhost:1313/categories/ - https://emin.software/tags/ + http://localhost:1313/tags/ diff --git a/public/tags/index.xml b/public/tags/index.xml index b52f548..fe2ed53 100644 --- a/public/tags/index.xml +++ b/public/tags/index.xml @@ -2,10 +2,10 @@ Tags on haxala1r - https://emin.software/tags/ + http://localhost:1313/tags/ Recent content in Tags on haxala1r Hugo en-us - +