useradd leaves the password field as '!'. After hardening sets UsePAM no,
sshd treats that account as locked and refuses even key logins, so the
bootstrap stopped with 'Key login failed after hardening'. Set the field to
'*' (no password, not locked).
The key-only deploy user has no password, so sudo for install-rubix.sh and
up.sh could never succeed. Add /etc/sudoers.d/90-rubix-<user> with NOPASSWD,
checked with visudo, and install sudo if the image lacks it.
- Note install flow is tested on Debian 13 (Trixie) in VPS setup steps
- Document COMPOSE_PROFILES default and optional metabase/mailcow stacks
- Explain Metabase auto sign-in and group-scoped analytics
- Add multi-company layout: shared server via work groups vs one VPS per tenant
- Refactor setup and maintenance sections so each shell command is in its own fenced code block
- Improve step-by-step execution clarity for operators running VPS bootstrap and deploy workflows
- Reclassify SQL migration, certbot, dialer, and release-update commands as extra/manual operations
- Keep the main install path focused on classic up.sh workflow without optional maintenance steps
- Remove existing host and host:port fingerprints before first password login test
- Prevent host key mismatch failures when reprovisioned VPS reuses the same IP or alias
- Update README section 2 to state DNS A/AAAA record alignment while editing .env
- Reduce setup ambiguity by tying domain host values and DNS changes to the same step
- Install docker.io only; add compose plugin from apt or GitHub release
- Fail clearly if docker compose is still missing after install
- README notes Compose v2 fallback on Debian