Framework version: 0.2.0
Collection of tools, scripts and utilities for Double Commander.
This repository is the single source of truth for all Double Commander tools.
Double Commander integrations use this repository directly.
Changes are developed, tested and validated through Gitea Actions.
double-commander-tools/
├── README.md
├── ARCHITECTURE.md
├── VERSION
│
├── deploy/
│ ├── deploy.py
│ └── tests/
│
├── scripts/
│ └── tool-name/
│
├── shared/
├── resources/
└── docs/
Every meaningful change follows this sequence:
./bin/test./bin/test includes the project rollout validation before the normal
ShellCheck, Python tests and deployment validation.
Each tool has its own version and follows the standard tool layout.
Example:
tool-name/
├── README.md
├── deploy.yml
│
├── config/
├── docs/
├── examples/
├── tests/
│
└── source files
The repository contains:
bin/rollout-check
This validator checks project-level rollout requirements including:
VERSION;pyproject.toml;.wikijs-publish.json;wikijs-publish version.The validator is executed automatically by:
./bin/test
Deployment is manifest driven and used for installation, recovery and migration.
Each tool contains a deploy.yml describing:
The deployment engine reads these manifests automatically for recovery and installation scenarios.
The deployment engine contains no tool-specific logic.
The repository framework version is stored in:
VERSION
The same framework version is also declared in pyproject.toml.
Framework releases follow Semantic Versioning:
Individual tools maintain their own version independently.
The rollout validator checks that the authoritative framework version and
the version in pyproject.toml remain consistent.