Copyparty

​

Towbar manifest

id: copyparty
name: Copyparty
buildServer: null
deployment:
  type: image
  image: copyparty/ac@sha256:0e276e2ca595d1b45df613573f094b789b9a8b41ff87cc55130db1ec9763c164
container:
  port: 3923
  network: application
  networkAlias: copyparty
  volumes:
    - name: w
      mountPath: /w
      initialData: image
    - name: cfg
      mountPath: /cfg
      initialData: image
environments:
  production:
    server: 192.0.2.10
rollout:
  type: recreate
  maintenanceMode: true
  reason: Persistent application data uses a single writer

​

Configure

1. Prepare the example server, connect the repository, and map production to the branch containing these manifests. Replace the example server IP. Commit the manifests, then sync the repository and inspect the resolved configuration.
2. Keep the Service’s named volumes attached across deployments. Towbar’s Datastore backup policy does not back up Service volumes, so include them in your own recovery plan.
3. This manifest has no public domain. Use a trusted connection to the server for the first check. Add a public route only after configuring the product’s authentication or an access gateway.
4. Deploy the Service, then perform the checks below before enabling auto-deploy.

​

Verify