Skip to content
mcoms edited this page Nov 21, 2025 · 1 revision

You can configure custom sync workflows for the --sync argument beyond the built-in all, force, partial, binaries and engine options.

Create a cliqueworkflows.json file next to CliqueSync.exe, and define a key to array mapping of workflows running a list of actions. For example:

{
    "custom": [
        "download_engine",
        "launch_project"
    ]
}

This will define a new "custom" sync workflow which can be run with ./CliqueSync --sync custom, which downloads the engine and then launches the project.

Refer to the actions Python script for available actions to use in a workflow.

Clone this wiki locally