Search docs.molo17.com

    DIY deployment guides

    This page collects manual deployment references for system administrators who must provision or customize the container environment themselves.

    Most users should not follow the DIY guides. Use the setup wizard at Get Gluesync; it provides the correct kit and automates the standard installation flow.

    When to follow the DIY path

    Continue only 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.

    • Your operations team accepts responsibility for runtime security, upgrades, storage, networking, and recovery.

    Manual reference guides

    • Offline installation and updates – install and update Gluesync in air-gapped environments using pre-downloaded platform archives and update packages.

    • Prepare Docker manually – Docker host requirements and administrator-controlled setup for Linux, macOS, and Windows Server.

    • Gluesync on Podman – install and run Gluesync on Podman, rootful or rootless, on Linux: Gluesync Control, offline install, manual setup, SELinux and troubleshooting.

    • Deploy with Docker Compose manually – how to review, customize, validate, and operate the Compose stack supplied by the setup wizard.

    • Deploy on Docker Swarm – install the Swarm kit on Linux or Windows Server 2022, and how Conductor updates and rolls back Swarm services.

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

    The DIY guides still assume that you obtained a current Gluesync kit through the Get Gluesync setup wizard. Use the kit’s helper tools (run.sh, or gluesync run on Windows Server) unless you have reviewed and deliberately replaced their behavior.