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>
49 lines
2.6 KiB
Plaintext
49 lines
2.6 KiB
Plaintext
---
|
||
title: Hosts SSH et proxy
|
||
description: Importez des hosts SSH enregistrés et ajoutez des transferts de ports SSH dans l’application desktop.
|
||
---
|
||
|
||
# Hosts SSH et proxy
|
||
|
||
Utilisez **Paramètres → Instances distantes** dans l’application desktop pour importer des hosts SSH enregistrés, vous connecter à une machine distante et rendre des ports supplémentaires disponibles via la même connexion SSH.
|
||
|
||
> Les hosts SSH et le proxy SSH sont des fonctionnalités **desktop uniquement**. Elles utilisent le client SSH de votre ordinateur.
|
||
|
||
## Importer un host SSH
|
||
|
||
OpenChamber peut lire les hosts depuis votre config SSH locale, le même endroit que les commandes comme `ssh work-server` utilisent.
|
||
|
||
1. Ouvrez **Paramètres → Instances distantes**.
|
||
2. Choisissez un host dans **Saved SSH hosts**.
|
||
3. Si le host est un pattern, saisissez la vraie destination, par exemple `deploy@app.example.com`.
|
||
4. Enregistrez et connectez-vous.
|
||
|
||
OpenChamber crée une instance distante avec cette commande SSH. Quand elle atteint **ready**, l’UI OpenChamber distante s’ouvre dans l’application desktop.
|
||
|
||
## Ajouter des transferts de ports
|
||
|
||
Chaque instance distante possède une section **Port Forwards**. Utilisez-la quand quelque chose d’un côté de la connexion SSH doit joindre un port de l’autre côté.
|
||
|
||
OpenChamber prend en charge trois types de transfert :
|
||
|
||
- **Local (-L)** — ouvre un port sur votre ordinateur qui se connecte à quelque chose sur la machine distante.
|
||
- **Remote (-R)** — ouvre un port sur la machine distante qui se reconnecte à votre ordinateur.
|
||
- **Dynamic (-D)** — ouvre un proxy SOCKS local via la connexion SSH.
|
||
|
||
Pour la plupart des aperçus d’app et dashboards qui tournent sur la machine distante, utilisez **Local (-L)**.
|
||
|
||
## Utiliser le proxy SOCKS
|
||
|
||
Choisissez **Dynamic (-D)** quand vous voulez que d’autres outils sur votre ordinateur naviguent via la machine distante. OpenChamber ouvre un port proxy SOCKS local pour cette connexion SSH.
|
||
|
||
Une fois la connexion prête, copiez ou utilisez l’adresse proxy locale depuis la ligne du transfert. Configurez votre navigateur ou outil pour l’utiliser comme proxy SOCKS5.
|
||
|
||
## Garder cela privé
|
||
|
||
Utilisez `127.0.0.1` ou `localhost` comme hosts de bind locaux, sauf si vous voulez volontairement que d’autres appareils de votre réseau atteignent le port transféré.
|
||
|
||
## Pages liées
|
||
|
||
- [Instances distantes](/remote-instances/) — connecter l’application desktop à OpenChamber sur une autre machine
|
||
- [Accès distant](/troubleshooting/remote-access/) — quand SSH ou l’accès distant ne se connecte pas
|