Mathieu Benoit
78e7cf55c6
VMs were created with user "erplibre" but NO password (lock_passwd: true), so the serial console refused every login and only SSH-by-key worked — hence "can't connect". - The todo deploy flow (single VM and infra) now sets a default console password "erplibre" for the "erplibre" user, in addition to the SSH key, so virsh console and password SSH both work. It is shown as "Console/SSH login: erplibre / erplibre" and can be changed at the single-VM prompt. - The console entry now prints the default login and the Ctrl+] hint. - After creating a VM, offer to add it to ~/.ssh/config (Host <name>, HostName <ip>, User erplibre) so "ssh <name>" just works; the infra flow asks once and adds every VM. Existing blocks for the same Host are replaced, the rest of the file is preserved, mode kept 600. Note: VMs created before this change have no console password — delete and redeploy them to get the erplibre/erplibre login. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| database_manager.py | ||
| kdbx_manager.py | ||
| logo_ascii.txt | ||
| README.base.md | ||
| README.fr.md | ||
| README.md | ||
| source_todo.sh | ||
| todo.json | ||
| todo.py | ||
| todo_example.json | ||
| todo_file_browser.py | ||
| todo_i18n.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.