A newer version of this documentation is available.
View Latest (v2.2)

DIY deployment guides

While the recommended path is to run the automated installers, some teams must follow hardened change-control processes or manage bespoke environments. This landing page collects all of the manual deployment references for those do-it-yourself (DIY) or sysadmin-only scenarios.

When to follow the DIY path

Choose these guides if:

  • Your organization mandates manual validation of each package and configuration step.

  • You need to adapt Gluesync to pre-existing Docker, Podman, or Kubernetes baselines.

  • Internet access to MOLO17 repositories is filtered and you must stage artifacts internally before rolling out Gluesync.

Manual reference guides

  • Install Docker – detailed Docker Engine installation flows for Linux and Windows, plus compose prerequisites.

  • Install Podman – distro-specific Podman and podman-compose instructions, including rootless operation hints.

  • Docker Compose deployment – how to run Gluesync with the full compose stack, monitoring, and reverse proxy.

  • Kubernetes deployment – describes the Helm charts, manifests, and tuning options for cluster administrators.

Each DIY document assumes you already downloaded the Gluesync kit and extracted it to the standard locations (/opt/gluesync on Linux, C:\\Program Files\\Gluesync on Windows, or /Applications/Gluesync on macOS). The kit ships with helper scripts (for example run.sh, run.ps1, and run-macos.sh) that wire credentials, compose overrides, and health checks automatically.