Podman-based deployment instructions
Expired Links
The download links expire automatically. Before proceeding, please ask clarity@chemotargets.com to re-activate them.
-
Create the working directory:
mkdir -p clrt4.2-artifacts cd clrt4.2-artifacts -
Download and load container images one by one:
for iname in helper frontend db backend; do echo "Loading clrt4-${iname}" curl -fsSL "https://dl.chmtgt.app/clrt4-${iname}.tar.zst" | sudo podman load done -
Download and load container volumes one by one:
- Option A: Download and load from disk (for unstable networks)
for vname in ct-license pg-data io-data; do echo "Downloading ${vname}.tar.zst to disk..." # 1. Download to disk using -o to enforce the correct filename if curl -fsSL "https://dl.chmtgt.app/${vname}.tar.zst" -o "${vname}.tar.zst"; then echo "Download complete. Restoring ${vname} to volume..." # 2. Mount the local file and the volume into Podman sudo podman run --rm \ -v "$PWD/${vname}.tar.zst:/tmp/${vname}.tar.zst:z" \ -v "${vname}:/srv/backup/${vname}:z" \ clrt4-helper sh -c "unzstd -c /tmp/${vname}.tar.zst | tar xf - -C /srv/backup" # 3. Clean up the large archive from the host machine rm -f "${vname}.tar.zst" echo "Successfully restored and cleaned up ${vname}." else echo "ERROR: Failed to download ${vname}. Link may be expired or invalid." fi done-
Option B: Load from pipe (for stable networks)
for vname in ct-license pg-data io-data; do echo "Streaming and restoring ${vname}..." curl -fsSL "https://dl.chmtgt.app/${vname}.tar.zst" | \ sudo podman run --rm \ -v "${vname}:/srv/backup/${vname}:z" \ clrt4-helper sh -c "unzstd | tar xf - -C /srv/backup" if [ ${PIPESTATUS[0]} -eq 0 ]; then echo "Successfully restored ${vname}" else echo "ERROR: Failed to fetch or restore ${vname}." fi done
-
Configure the podman quadlet:
sudo mkdir -p /etc/containers curl -fsSL "https://dl.chmtgt.app/clrt4-quadlet-setup.tar.gz" \ | sudo tar xzf - --strip-components=1 -C /etc/containers/ sudo systemctl daemon-reload -
Start the pod service
sudo systemctl start clrt4-app-pod -
Wait ~15 min for the first run to populate the backend cache.