From 0d0add88c3f57cd5a3cc00cf9303944442012bb6 Mon Sep 17 00:00:00 2001 From: Emin Arslan Date: Sun, 27 Oct 2024 23:34:11 +0300 Subject: [PATCH] Fixed some paragpaph formattings --- content/posts/podman-setup.md | 28 +++++++++++++++------------- 1 file changed, 15 insertions(+), 13 deletions(-) diff --git a/content/posts/podman-setup.md b/content/posts/podman-setup.md index 8d43b28..b2d57e4 100644 --- a/content/posts/podman-setup.md +++ b/content/posts/podman-setup.md @@ -104,18 +104,20 @@ $ podman rm Pods are basically just a collection of containers - multiple programs working 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. +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. -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 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. +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 +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. +On top of this, pods can be built purely from a kubernetes-compatible configuration +file, so setting them up is relatively easy.