You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/post/immortal-host/index.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,8 @@ tags:
8
8
---
9
9
10
10
## Introduction
11
-
12
-
Immortal Hosting is not just a standard hosting provider; it is a sophisticated, self-managed infrastructure project designed to deliver high-performance application and game server hosting. Built on a foundation of modern DevOps practices, it leverages container orchestration, edge computing, and high-availability database clusters to ensure resilience and scalability.
11
+
[Immortal Hosting](https://immortal.host)
12
+
is not just a standard hosting provider; it is a sophisticated, self-managed infrastructure project designed to deliver high-performance application and game server hosting. Built on a foundation of modern DevOps practices, it leverages container orchestration, edge computing, and high-availability database clusters to ensure resilience and scalability.
13
13
14
14
Below is a technical resume of the architecture and technologies currently powering the **Immortal.host** ecosystem.
15
15
@@ -35,13 +35,15 @@ At the heart of Immortal Hosting lies a commitment to modern containerization an
35
35
Efficiency and reliability are driven by automated pipelines, ensuring that code moves from development to production seamlessly.
36
36
37
37
***Managed Private Gitea:** The ecosystem is powered by a private, self-managed **Gitea** instance. This acts as the central hub for version control, hosting both application source code and Infrastructure-as-Code (IaC) repositories securely.
38
+

38
39
***CI/CD Runners:** Integrated CI/CD runners are deployed to automate the software lifecycle. These runners handle testing, building, and deploying applications directly to the Kubernetes clusters, ensuring rapid iteration cycles and consistent delivery.
39
40
40
41
## Identity & Access Management
41
42
42
43
Security starts with identity. To protect the ecosystem, a unified authentication layer has been implemented across the board.
43
44
44
45
***Authentik:** The infrastructure relies on **Authentik** as the central Identity Provider (IdP). This creates a seamless Single Sign-On (SSO) experience while enforcing strict access policies for all internal tools and panels.
46
+

45
47
46
48
## Database Architecture
47
49
@@ -55,6 +57,7 @@ Data integrity and availability are prioritized.
55
57
A primary function of the infrastructure is hosting low-latency, high-performance game servers.
56
58
57
59
***Pelican Panel:** The infrastructure utilizes **Pelican Panel**, a modern, open-source game server management panel. This provides a centralized interface for deploying and managing game server instances.
60
+

58
61
***GTA V / FiveM:** A key workload includes **FiveM** servers, optimized for GTA V roleplay and gaming communities. The network is tuned to handle the UDP traffic and real-time demands of multiplayer gaming.
59
62
60
63
## Networking & Security
@@ -73,13 +76,18 @@ The network stack is designed for speed, security, and ease of management, utili
73
76
Maintaining high uptime requires vigilance and a proactive stance on support.
74
77
75
78
***Continuous Monitoring:** The health of the infrastructure is tracked in real-time. Automated monitoring systems keep a pulse on server metrics, container health, and network latency.
79
+

80
+
76
81
***Unbeaten Support:** Beyond the code, the human element is a core pillar. As the founder, I provide responsive, technical support, bridging the gap between complex hosting infrastructure and end-user needs.
82
+

77
83
78
84
## Web Development
79
85
80
86
Beyond infrastructure, the ecosystem supports custom web applications.
81
87
82
88
***Next.js (React):** The frontend components (such as landing pages or status dashboards) are built using **Next.js**. This allows for a reactive, component-based UI, capable of handling dynamic content like live server stats or image carousels with multi-language support (English/French).
0 commit comments