haxala1r/blog
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fixed some paragpaph formattings

Browse Source
This commit is contained in:
Emin Arslan 2024-10-27 23:34:11 +03:00
parent 77c1d49f83
commit 0d0add88c3
1 changed files with 15 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
content/posts/podman-setup.md
View File

@ -104,18 +104,20 @@ $ podman rm <id>
Pods are basically just a collection of containers - multiple programs working with each other. 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, Usually, on a server, each application *isn't* totally separate from each other
I want my git server (e.g. gogs) to automatically build and update my website whenever I push to its git - for my own usecase, I want my git server (e.g. gogs) to automatically build
repository. That means my git server and web server can't be *totally* separate, there's some amount of and update my website whenever I push to its git repository. That means my git
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. Pods allow you to create a "pod" containing several containers, sharing resources
For example, I could run a pod with nginx and gogs running in seperate containers - then, the nginx with each other, etc. For example, I could run a pod with nginx and gogs running
server could act as a reverse proxy based on host name, showing the web page on emin.software, in seperate containers - then, the nginx server could act as a reverse proxy based
and the git server on git.emin.software. Nginx redirects to gogs which only binds to *the pod's localhost on host name, showing the web page on emin.software, and the git server on
address*, so only nginx can reach it. Likewise, a database server can be added to the pod only for the git.emin.software. Nginx redirects to gogs which only binds to *the pod's
git server to use, so that it can't be reached from the outside the pod - and it is logically grouped localhost address*, so only nginx can reach it. Likewise, a database server can
along with the rest of the pod. 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 On top of this, pods can be built purely from a kubernetes-compatible configuration
up is relatively easy. file, so setting them up is relatively easy.