Update README.md
This commit is contained in:
11
README.md
11
README.md
@@ -2,13 +2,11 @@
|
||||
|
||||
## Description
|
||||
|
||||
LXC containerized Apache webserver hosted within Proxmox.
|
||||
LXC containerized Apache webserver, hosted within Proxmox, featuring a fully automated deployment via Ansible
|
||||
|
||||
Serving a static HTML page, acting as the Intranet.
|
||||
Serving a static HTML page, acting as the Intranet, providing a quick, user accessible way to reach internal only services
|
||||
|
||||
This provides a quick, user accessible way to reach internal only services.
|
||||
|
||||
Featuring an Ansible playbook automating deployment.
|
||||
Additionally serving as a place to host temporary files within the LAN, and providing a centarlized place to monitor my SSL cert health and expiry dates
|
||||
|
||||
## Architecture Diagram
|
||||
|
||||
@@ -33,6 +31,7 @@ Featuring an Ansible playbook automating deployment.
|
||||
- Apache
|
||||
- A reserved or static IP
|
||||
- Any modern browser capable of setting a custom home page
|
||||
- Debian
|
||||
|
||||
## Creation Notes
|
||||
|
||||
@@ -42,7 +41,7 @@ Consequently I decided to create and configure an LXC containerized Apache insta
|
||||
|
||||
Apache's function is to serve a static HTML page, acting as the Intranet
|
||||
|
||||
The container was given a bridged IP and granted a DHCP reservation allowing centralized management
|
||||
The container was given a bridged IP and granted a DHCP reservation
|
||||
|
||||
Apache and LXC containerization were chosen due to their extremely low resource requirement
|
||||
|
||||
|
||||
Reference in New Issue
Block a user