Les outils de la phase « après » vivent DANS le dépôt : la compilation mobile, l'AVD, et maintenant le script Forgejo. Sur une VM « bureau seul », sans clone, ils n'existent pas — et ils étaient écartés en silence. Une case cochée passait donc pour honorée. La commande le dit désormais, en nommant les outils concernés. Trois lignes qui évitent de chercher pourquoi la forge demandée n'est nulle part. --- EN --- The "after" phase tools live IN the repository: the mobile build, the AVD, and now the Forgejo script. On a desktop-only VM, with no clone, they do not exist — and they were dropped in silence. A ticked checkbox therefore passed for honoured. The command now says so, naming the tools concerned. Three lines that save hunting for why the requested forge is nowhere to be found. Assisted-by: Claude Opus 5 |
||
|---|---|---|
| .. | ||
| auto_ask.py | ||
| database_manager.py | ||
| kdbx_manager.py | ||
| logo_ascii.txt | ||
| migration_form.py | ||
| migration_stats.py | ||
| migration_status.py | ||
| migration_status_tui.py | ||
| qemu_deploy_form.py | ||
| qemu_install_monitor.py | ||
| README.base.md | ||
| README.fr.md | ||
| README.md | ||
| source_todo.sh | ||
| textual_setup.py | ||
| todo.json | ||
| todo.py | ||
| todo_example.json | ||
| todo_file_browser.py | ||
| todo_i18n.py | ||
| todo_prefs.py | ||
| todo_telemetry.py | ||
| todo_upgrade.py | ||
| version_manager.py | ||
TODO is an assistant robot to use ERPLibre
Execute it with ./script/todo/todo.py or make todo.
For a new project, copy todo_example.json to private/todo/todo_override.json | private/todo/todo_override_private.json and edit it.
The mail/ package is the mail client reachable from Assistant > Mail:
several IMAP/SMTP accounts, a local cache, and a Textual TUI. See
../../doc/EMAIL.md.