Docker Compose Deployment through Komodo

[Manuel06p]

I personally use Komodo to manage my Docker stacks and deployments. It provides a clean Web UI for managing Docker Compose services. After a few attempts, I managed to self-host Any-Sync through it and wanted to share my configuration to help others get it running more easily.

1. Adding the Any-Sync Repository

The first step is adding a new repository in the Komodo Repos section. Here’s the TOML configuration I used:

[[repo]]
name = "any-sync"
[repo.config]
server = "server-00"
repo = "anyproto/any-sync-dockercompose"
path = "/srv/docker/any-sync"

⚠️ Tip: Specifying a path ensures the repo is cloned into a dedicated folder, making it easier to manage all created files. I keep all of my stacks under a single folder.

Once the repo is added, you can both clone it and pull updates directly from the Web UI.

2. Creating the Any-Sync Stack

Next, create a stack in the Komodo Stacks section. When creating it, select:

• Mode: Git Repo (to manage files via the repository)

• Repo: The previously added any-sync repo

Here’s the TOML I used for the stack:

[[stack]]
name = "any-sync"
[stack.config]
server = "server-00"
linked_repo = "any-sync"
file_paths = ["docker-compose.yml"]
env_file_path = ".env.override"
additional_env_files = [".env"]
pre_deploy.command = """
  # Multiple commands supported; comments allowed
docker buildx build --load --tag generateconfig-env --file Dockerfile-generateconfig-env .
docker run --rm --volume ./:/code/:Z generateconfig-env
"""
extra_args = [
  "--remove-orphans --quiet-pull"
]
ignore_services = [
  "any-sync-coordinator_bootstrap",
  "create-bucket",
  "generateconfig-anyconf",
  "generateconfig-processing"
]
environment = """
  # VARIABLE = value
ANY_SYNC_NODE_VERSION=latest
ANY_SYNC_FILENODE_VERSION=latest
ANY_SYNC_COORDINATOR_VERSION=latest
ANY_SYNC_CONSENSUSNODE_VERSION=latest
STORAGE_DIR=/mnt/data/docker/any-sync/data
EXTERNAL_LISTEN_HOSTS=any-sync.domain.com
"""

3. Notes on Configuration

• Pre-deploy commands: I analyzed the Makefile to replicate its steps in a way compatible with Komodo. The two pre_deploy.command steps above generate necessary configuration files together with the extra args.

• Ignored services: The four bootstrap services are ignored so the stack appears healthy in the Web UI.

• Compose file: The main Compose file must be explicitly set to docker-compose.yml, as Komodo defaults to compose.yaml.

• Environment variables: Using .env.override as the main env file allows you to manage custom variables through the Web UI. You also need to add .env as an additional env file for the app to run correctly.

4. Summary

Configuring Any-Sync with Komodo was initially a bit complex, but once set up, the Web UI makes managing updates and deployments much easier. I hope this guide helps anyone looking to self-host Any-Sync using Komodo.

Disclaimer

I am not affiliated with Komodo in any way; I’m simply sharing my experience to help the community. On a personal note, I really enjoy using Anytype and appreciate the work the team has done—it’s a fantastic tool!

[compgeniuses]

would be interesed to build this for Nethserver 8