33 lines
850 B
Markdown
33 lines
850 B
Markdown
|
# Core Stack
|
||
|
|
|
||
|
|
## Description
|
||
|
|
|
||
|
|
This page documents the known core software stack running in the homelab.
|
||
|
|
|
||
|
|
## Current configuration
|
||
|
|
|
||
|
|
- Docker
|
||
|
|
- Portainer
|
||
|
|
- Nginx Proxy Manager
|
||
|
|
|
||
|
|
## Known facts
|
||
|
|
|
||
|
|
- Docker is used as part of the core stack.
|
||
|
|
- Portainer is used as part of the core stack.
|
||
|
|
- Nginx Proxy Manager is used as part of the core stack.
|
||
|
|
|
||
|
|
## Unknown / needs clarification
|
||
|
|
|
||
|
|
- Docker version.
|
||
|
|
- Docker installation method.
|
||
|
|
- Whether Docker Compose is used.
|
||
|
|
- Location of Compose files, stack files, or deployment manifests.
|
||
|
|
- Portainer deployment method.
|
||
|
|
- Portainer exposed URL or access method.
|
||
|
|
- Nginx Proxy Manager deployment method.
|
||
|
|
- Nginx Proxy Manager exposed URL or access method.
|
||
|
|
- Container restart policies.
|
||
|
|
- Container network names and topology.
|
||
|
|
- Persistent volume locations.
|
||
|
|
- Backup method for Portainer and Nginx Proxy Manager data.
|