# proxmox-utils (EXPERIMENTAL) A set of scripts for automating setup and tasks in proxmox. ## TODO - revise defaults - separate templates/assets into distribution and user directories ...this is needed to allow the user to change the configs without the fear of them being overwritten by git (similar to how config is handlerd) - automate: - create/destory -- DONE - updates - backup/restore - basic infrastructure CT's - ns -- DONE - gate / reverse proxy -- DONE - basic service CT's - syncthing -- DONE - git -- DONE - nextcloud -- DONE - vpn -- DONE - ssh -- DONE - mail - basic recurent tasks - backups - archiving - updates - ... ## Architecture XXX service structure XXX network In general `proxmox-utils` splits the configuration into two levels: ### CT level This level is handled by the `Makefile` and is almost completely automated ### Host level This level depends on the host setup and is currently done manually depending on existing host configuration. XXX clean setup scripts... ## Prerequisites ### Proxmox ```shell sudo apt update && sudo apt upgrade ``` ```shell sudo apt install git make ``` ### Network Bridges `proxmox-utils` expects there to be at least three bridges: - `WAN` - connected to the port that faces the external network (either directly of via a router) - `LAN` - a virtual bridge, not connected to any physical interfaces - `ADMIN` - connected to a second physical interface used for administrative purposes. Note their numbers (i.e. the number in `vmbr#`), this will be needed for setup. ### DNS Add `10.1.1.1` to the DNS on the Proxmox host node after the `127.0.0.1` but before whatever external DNS you are using. ### Firewall Make sure to allow at least `ssh` access to the host node from the `ADMIN` interface to allow admin CT's access to the host if needed, this is mostly needed to allow VPN/ssh administration from outside. For Proxmox firewall configuration see: https://pve.proxmox.com/wiki/Firewall ## Setup ```shell sudo make all ```