jubnl
5c3b89578d
- Add wiki/Install-Proxmox.md with full install/update/log instructions - Add Proxmox VE section to wiki/Updating.md - Add Install: Proxmox VE (LXC) to wiki/_Sidebar.md - Add "Proxmox Community Script" option to bug report install dropdown - Exclude GitHub meta files from triggering Docker CI workflow
2.8 KiB
Install: Proxmox VE (LXC)
Install TREK on Proxmox VE as an LXC container using the Proxmox VE Community Scripts.
A big thank you to the members of community-scripts for adding TREK to their collection and maintaining the install and update scripts.
Prerequisites
- Proxmox VE with shell access
- Internet access from the Proxmox host
Install
Run the following command in the Proxmox VE Shell:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/trek.sh)"
Tip: Always verify the latest command on the community-scripts TREK page before running — the script URL may change between releases.
The script will prompt you to choose between Default and Advanced settings.
Default container specs
| Resource | Value |
|---|---|
| OS | Debian 13 |
| CPU | 2 cores |
| RAM | 2048 MB |
| Storage | 8 GB |
| Port | 3000 |
The container is unprivileged. TREK is installed at /opt/trek.
After Install
Once the container starts, open your browser at:
http://<container-ip>:3000
On first boot, TREK automatically creates an admin account. The credentials are printed to the container log — check them with:
journalctl -u trek -n 50
The ENCRYPTION_KEY is auto-generated during setup and saved to /opt/trek/server/.env. Record that file in your backups.
Viewing Logs
TREK runs as a systemd service named trek inside the LXC. To view logs from within the container:
# Follow live logs
journalctl -u trek -f
# Show last 100 lines
journalctl -u trek -n 100
# Show logs since last boot
journalctl -u trek -b
To access the container shell from the Proxmox VE host, click the container in the UI and open Console, or run:
pct enter <container-id>
Configuration
The environment file is located at /opt/trek/server/.env inside the container. Edit it to set variables like ALLOWED_ORIGINS, APP_URL, or TZ, then restart the service:
systemctl restart trek
See Environment-Variables for the full variable reference.
Updating
The script supports in-place updates via the community scripts update mechanism. In the Proxmox VE Shell, run the same install command again and select Update when prompted, or use the community scripts update helper if you have it installed.
The update process automatically backs up your data and uploads before applying the new release, then restores them afterward.
Next Steps
- Environment-Variables — complete variable reference
- Reverse-Proxy — put TREK behind Nginx or Caddy
- Updating — general update notes