docs(D1): README EN/FR + ENTERPRISE recadrés IDE multi-projet + app native

README.md et README.fr.md (miroir strict, 18 sections) : tagline et « What Arboretum does » recadrés vers l'IDE IA multi-projet (arbre unique, onglets, dock terminaux, panneaux git), nouvelle section « Desktop app » / « Application de bureau » (3 OS, runtime embarqué donc pas de Node à installer côté app, auto-update, SmartScreen/Gatekeeper), « The IDE, workspace & git operations » réécrit, « Requirements » précisé. Pas d'URL d'artefact inventée (page des releases + packages/desktop).

docs/ENTERPRISE_DEPLOYMENT.md : app desktop = client autonome additif (daemon local embarqué), déploiement serveur inchangé. 0 tiret (garde CI).
This commit is contained in:
2026-07-17 18:14:25 +02:00
parent 1299b1b349
commit 0532331795
3 changed files with 50 additions and 24 deletions

View File

@@ -3,6 +3,12 @@
This guide complements [`../SECURITY.md`](../SECURITY.md) with the operational steps a regulated or
security-conscious organization needs to deploy Arboretum with confidence.
> **Desktop app.** The Electron desktop app (`packages/desktop`) is an additive, self-contained
> client: it runs its own local daemon (child process) bound to `127.0.0.1` and shows the same web
> UI. It does not change the server deployment below; a shared or service daemon (systemd/launchd,
> reached over Tailscale Serve) is deployed exactly as described here, independently of whether
> developers also use the desktop app on their own machines.
## 1. Remote access: Tailscale Serve (recommended)
Never open a public port. Keep the default `127.0.0.1` bind and put Arboretum behind Tailscale Serve: