Skip to main content

Server configuration tree

The public repository now contains a reviewed configuration tree covering the Proxmox host and all nine established container roles. It is a selected export, not a full filesystem copy or a complete infrastructure rebuild kit.

Browse the server tree

Structure​

server/
README.md
configuration-notes.md
host/proxmox/lxc/ selected settings for nine containers
containers/
docs/ documented nginx locations and example links
forgejo/ selected settings and configuration location
tailscale/ forwarding settings and unit paths
nextcloud-private/ cron service, timer and unit paths
nextcloud-secondary/ cron service, timer and unit paths
caddy-proxy/ main import and imported routing template
netbird/ Caddy configuration template and unit paths
runner/ systemd service and Docker group drop-in
miniflux/ selected configuration settings and unit paths

Role directories do not rename deployed containers. They also do not establish that every application, route or authorization policy is functional.

Dependency graphs​

These diagrams separate placement, request paths and delivery dependencies. Arrows are labelled: placement is not a network connection. Dashed edges show saved configuration, deferred integration or manual steps as labelled, not a claim of verified reachability. Addresses and credentials are intentionally absent.

1. Host and container placement​

All nine role containers have observed resource definitions. This does not establish that every application or authorization policy is complete. No additional development container is shown as deployed.

2. Public access, administration and configured routes​

2.1 Public tunnel paths​

2.2 Private administration​

2.3 Saved routes and deferred application access​

The tunnel connector and the latter Caddy instance share a container role, but public tunnel traffic is not shown passing through Caddy. LAN checks in the saved Caddy files do not cover every earlier client handler and are not presented as a complete NetBird authorization policy. Public SSH is not implied.

3. Documentation and application dependencies​

3.1 Private documentation delivery​

3.2 Public static publication​

3.3 Private Nextcloud application stack​

3.4 Miniflux database dependency​

The application stack is based on project documentation; this update did not retest database, cache or storage behavior. The cron unit files were read in both Nextcloud containers, but their execution was not tested. The cron arrow does not mean PHP CLI calls PHP-FPM. Private image delivery and manual public static publication are different release paths. Deliberate rollback testing remains unfinished.

Observed container settings​

Read on 22 November 2026. All nine report amd64, Debian and unprivileged mode. Memory and swap values are configured MiB limits, not measured consumption.

RoleCPU core limitMemory MiBSwap MiBHost-start autostart
Documentation1512256enabled
Forgejo22048512disabled
Tailscale1512256enabled
Private Nextcloud230721024disabled
Secondary Nextcloud230721024disabled
Caddy proxy1512512disabled
NetBird-related components22048512disabled
Actions runner240961024disabled
Miniflux11024512enabled

Disabled host-start autostart does not mean a container is stopped. CPU limits are not dedicated physical cores. The fragments omit network and storage settings and must never replace a complete live container definition.

Included evidence​

  • Selected Proxmox resource and feature fields for all nine roles.
  • A runner service and its Docker supplementary-group drop-in.
  • Identical observed Nextcloud cron services and timers in both related containers.
  • Saved IPv4 and IPv6 forwarding settings for the Tailscale subnet router.
  • Caddy templates derived from the current main and imported files.
  • Selected Miniflux settings, excluding the database credential file.
  • Unit-definition paths, with loaded definitions distinguished from active services.

Security and omissions​

Private addresses, the observed public IPv6 interface address, credentials, private keys, application data, logs and backup contents are not exported. Credential paths and environment variable references are not credential values. Templates contain placeholders and are not directly installable.

Application authorization and rollback tests remain separate tasks. In particular, the NetBird configuration is not presented as a completed access-control deployment.

Selected file map

Configuration examples