Teknium
48465c3933
Cron jobs are scheduled work bound to the source profile and its origin channel. A clone that inherited cron/jobs.json fired every job twice: two gateways with identical job ids running the same weekly jobs in parallel (double spend, duplicate deliveries) until one gateway died. Root cause: `cron` was not in _CLONE_ALL_HISTORY_EXCLUDE_ROOT, so the copytree in _clone_all_into carried jobs.json along. Add it to the per-profile history exclude set (applies to any source, CLI, dashboard and TUI/desktop RPC all funnel through create_profile), recreate the _PROFILE_DIRS skeleton after the copy so the clone still has an empty cron/ (and sessions/), and say so in the CLI summary line and docs. --clone (config-only) never copied cron; export/backup keep cron as before (an archive is a portable snapshot, not a second live profile).
Website
This website is built using Docusaurus, a modern static website generator.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.