homelab/docs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: Updates to network article.
All checks were successful
CI / release (push) Successful in 6m9s
Details

Browse Source
This commit is contained in:
Michael Housh
2025-04-08 13:36:39 -04:00
parent d0383b0d4e
commit a53e808aec
10 changed files with 122 additions and 50 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
content/articles/2025-04-04-servers.md
View File

@@ -1,6 +1,8 @@
---
date: 2025-04-04
updated: 2025-04-08
tags: servers, infrastructure, homelab
primaryTag: infrastructure
---
# Servers
@@ -15,7 +17,9 @@ services based on that. Meaning services that I run primarily for personal items
are running on servers that I own, while services that are supporting business
functionality run on the companies server.
All of the servers run the services in `Docker Containers`.
All of the servers run the services in `Docker Containers`, which allows for
them to be isolated from the host system (server) and makes them more easily
portable between servers if needed.
There is also a `Raspberry-Pi` that runs `Home Assitant`, which is another one
of my personal devices.
@@ -27,10 +31,14 @@ of my personal devices.
| rogue-mini | roguemini.housh.dev | 192.168.50.4 |
| home-assistant | homeassitant.housh.dev | 192.168.30.5 |
| NAS | nas.housh.dev | 192.168.10.105 |
| Backup NAS | nas.hhe | 192.168.1.10 |
You can read more about the network setup
[here](https://docs.housh.dev/articles/2025/network/).
> Note: The backup NAS is used to backup our primary NAS, for now it is not easy
> to use, and will be used for camera / security footage in the future.
## Containers
Services run inside of docker containers that are spread between several
@@ -44,7 +52,8 @@ is hosted on an [internal git server](https://git.housh.dev/homelab). The
configuration will consist of a docker compose file (generally named
`compose.yaml`). There is often an `example.env` file for the service, these are
examples for documentation and variable naming purposes. The environment
variables themselves are setup in the container orchestrator for the service.
variables themselves are setup in the container orchestrator for the service to
prevent sensitive data being "leaked".
### Container orchestrator
@@ -99,7 +108,7 @@ access may be implemented in the future. If access is required outside of our
network then using our VPN is required. The VPN setup is done automatically via
unifi (our network router).
`DNS` is what translates domain names to `IP` addresses, currently the public
`DNS` is what translates domain names to `IP addresses`, currently the public
DNS records are handled by cloudflare. Cloudflare is used to validate that we
own the `housh.dev` domain name in order for Let's Encrypt to issue free `TLS`
certificates. TLS is used to encrypt traffic over the web (`https://`).
@@ -107,4 +116,7 @@ certificates. TLS is used to encrypt traffic over the web (`https://`).
Internal DNS records are setup in our unifi router `Settings -> Routing -> DNS`.
The internal DNS is fairly simple and just needs to map to servers appropriately
(primarily just to the primary caddy instance, which then handles all the
routing to the individual service that is requested).
routing to the individual service that is requested). All devices that connect
to the network will be able to use the internal DNS to resolve host names
properly (meaning it all should just work automatically without any knowledge
from the user).