Pascal AndréandBohdan Triapitsyn
49a1424e5f
* feat: add French locale runtime Add French to OpenChamber's shared i18n runtime, dictionaries, and parity tests so the existing language picker can load a complete fr locale across shared UI surfaces. * fix: localize shared UI formatting Remove remaining shared UI locale hardcodings so dates, numbers, and first-party helper copy follow the active app locale instead of leaking English on French surfaces. * feat: localize VS Code French surfaces Localize VS Code bootstrap, native runtime messages, panel titles, and manifest contribution strings so French users get consistent first-party copy across the extension experience. * fix: TASK-2026-05-30-008 correct French review findings Fix broken French relative-time and weekday strings reported on PR #1482 and restore proper import order in quota utils without broadening scope. * fix: TASK-2026-05-30-008 address final PR review comments Capture the localized More Info label once in the VS Code CLI-missing flow and replace the remaining inline French-only utility strings with dictionary-driven copy plus required locale keys. * fix: TASK-2026-05-30-008 normalize French glossary Correct glossary-level French terminology on the live PR branch, keeping canonical technical terms like PR, worktree, stash, HEAD, Mermaid, Markdown, remote, and session while replacing misleading literal translations. * fix: TASK-2026-05-30-008 refine French terminology pass Clean up remaining glossary mistakes on the French PR branch, especially around Mermaid, Markdown, PR, worktree, stash, branch, remote, and commit terminology, while keeping behavior unchanged. * fix: TASK-2026-05-30-008 clean remaining French false friends Correct the SOCKS5 mistranslation and a final small set of obvious false-friend technical nouns on the French branch without changing behavior. * fix: TASK-2026-05-30-008 correct French glossary terms Replace remaining false-friend translations in the French UI dictionaries and normalize technical labels for the French PR branch. * fix: TASK-2026-05-30-008 remove remaining French Mermaid false friend Replace the last confirmed Sirène translation with Mermaid and re-run the requested blacklist and build verification on the PR branch. * fix: TASK-2026-05-30-008 enforce French glossary policy Keep skill/PR/worktree/remote terminology developer-credible in French and remove remaining machine-translated Git and settings copy. * fix: TASK-2026-05-30-008 keep prompt terminology in French Replace remaining technical invite translations with prompt wording across scheduled tasks, multi-run, prompt templates, and Magic Prompts. * fix: TASK-2026-05-30-008 finalize French terminology cleanup Polish remaining worktree/remote wording, remove visible metadata leakage, and correct final Git and settings labels on the French PR branch. * fix: TASK-2026-05-30-008 polish final French strings Correct the last aria-like artifacts and awkward worktree/remote/GitHub URL phrasing in the French dictionaries. * fix: TASK-2026-05-30-008 normalize final French glossary framing Tighten the last worktree/remote/checkout wording and fix remaining French grammar around canonical technical terms. * fix: TASK-2026-05-30-008 align final developer glossary wording Normalize the last French framing around canonical developer terms like worktree, remote, prompt, and checkout. * fix: TASK-2026-05-30-008 harmonize final French sentence framing Replace the last raw franglais around checkout, remote, worktree, and prompt-facing labels with more natural French framing while keeping the chosen technical terms. * fix: TASK-2026-05-30-008 add compact relative date keys Replace French-specific prefix stripping in compact session date labels with dedicated i18n keys across locale dictionaries, preserving existing compact label output while making French wording robust. * docs: add French documentation * docs: mention French locale folder --------- Co-authored-by: Bohdan Triapitsyn <artmore@protonmail.com>
118 lines
3.5 KiB
Plaintext
118 lines
3.5 KiB
Plaintext
---
|
||
title: Tunnels
|
||
description: Exposez OpenChamber en sécurité pour l’accès distant et mobile.
|
||
---
|
||
|
||
# Tunnels
|
||
|
||
Un tunnel est un lien public vers votre OpenChamber, pour y accéder depuis votre téléphone ou un autre réseau. Utilisez `openchamber tunnel` pour en créer un pour une instance en cours d’exécution.
|
||
|
||
## Prérequis
|
||
|
||
OpenChamber démarre la CLI du fournisseur de tunnel sur votre machine. Installez d’abord le fournisseur que vous voulez utiliser :
|
||
|
||
```bash
|
||
brew install cloudflared
|
||
brew install ngrok
|
||
```
|
||
|
||
Les tunnels rapides Cloudflare peuvent fonctionner avec `cloudflared`. Ngrok nécessite un compte ngrok et un authtoken depuis le dashboard ngrok :
|
||
|
||
```bash
|
||
ngrok config add-authtoken <your-ngrok-token>
|
||
```
|
||
|
||
## Démarrage rapide
|
||
|
||
1. Démarrez OpenChamber :
|
||
|
||
```bash
|
||
openchamber
|
||
```
|
||
|
||
Si vous sautez cette étape, `openchamber tunnel start` peut démarrer automatiquement un serveur CLI. Lors de l’auto-démarrage, vous pouvez passer des options serveur comme `--port`, `--host`, `--lan`, `--ui-password` et `--api-only`.
|
||
|
||
2. Démarrez un tunnel Cloudflare :
|
||
|
||
```bash
|
||
openchamber tunnel start --provider cloudflare --mode quick
|
||
```
|
||
|
||
Ou démarrez un tunnel Ngrok :
|
||
|
||
```bash
|
||
openchamber tunnel start --provider ngrok --mode quick
|
||
```
|
||
|
||
3. Vérifiez l’état :
|
||
|
||
```bash
|
||
openchamber tunnel status
|
||
```
|
||
|
||
Quand le tunnel est actif, `status` affiche une URL publique. Ouvrez-la, ou scannez le QR code, pour joindre OpenChamber depuis n’importe où.
|
||
|
||
Par défaut, OpenChamber affiche un QR code dans les sessions TTY interactives. Utilisez `--qr` pour forcer la sortie QR, ou `--no-qr` pour la désactiver.
|
||
|
||
## Fournisseurs
|
||
|
||
- `cloudflare` : modes quick, managed remote et managed local
|
||
- `ngrok` : mode quick
|
||
|
||
## Modes gérés
|
||
|
||
### Managed remote
|
||
|
||
Utilisez un token + hostname gérés par Cloudflare :
|
||
|
||
```bash
|
||
openchamber tunnel start --provider cloudflare --mode managed-remote --token-file ~/.secrets/cf-token --hostname app.example.com
|
||
```
|
||
|
||
### Managed local
|
||
|
||
Utilisez une configuration `cloudflared` locale :
|
||
|
||
```bash
|
||
openchamber tunnel start --provider cloudflare --mode managed-local --config ~/.cloudflared/config.yml
|
||
```
|
||
|
||
## Profils (managed-remote)
|
||
|
||
Enregistrez un profil réutilisable :
|
||
|
||
```bash
|
||
openchamber tunnel profile add --provider cloudflare --mode managed-remote --name prod-main --hostname app.example.com --token-file ~/.secrets/cf-token
|
||
```
|
||
|
||
Démarrez avec le profil enregistré :
|
||
|
||
```bash
|
||
openchamber tunnel start --profile prod-main
|
||
```
|
||
|
||
## Commandes utiles
|
||
|
||
```bash
|
||
openchamber tunnel providers
|
||
openchamber tunnel ready --provider cloudflare
|
||
openchamber tunnel ready --provider ngrok
|
||
openchamber tunnel doctor --provider cloudflare
|
||
openchamber tunnel doctor --provider ngrok
|
||
openchamber tunnel stop --port 3000
|
||
```
|
||
|
||
## Notes de comportement
|
||
|
||
- un tunnel actif par instance OpenChamber (port)
|
||
- démarrer un nouveau mode/fournisseur sur la même instance remplace le tunnel précédent
|
||
- générer un nouveau lien de connexion révoque le précédent lien inutilisé
|
||
- l’auto-démarrage du tunnel conserve les flags serveur comme `--ui-password` et `--api-only` dans les paramètres d’instance utilisés par les flux de redémarrage/mise à jour
|
||
|
||
## Pages liées
|
||
|
||
- [Sécurité](/security/) — protéger l’UI avant de l’exposer
|
||
- [Tunnels desktop](/desktop-tunnels/) — configuration des tunnels de l’application desktop sans démarrage CLI
|
||
- [PWA et mobile](/mobile/) — joindre OpenChamber depuis votre téléphone
|
||
- [Dépannage](/troubleshooting/) — si le lien de tunnel ne fonctionne pas
|