i18n - docs translations (#19955)
Created by Github action Co-authored-by: github-actions <github-actions@twenty.com>
This commit is contained in:
github-actions[bot]
committed by
GitHub
GitHub
parent
11fd3bd6ee
commit
800d0f28ff
@@ -5,37 +5,37 @@ icon: arrow-up-right-dots
|
||||
|
||||
## إرشادات عامة
|
||||
|
||||
**Always back up your database before starting the upgrade process** by running:
|
||||
**احرص دائمًا على إنشاء نسخة احتياطية لقاعدة البيانات قبل بدء عملية الترقية** عن طريق تشغيل:
|
||||
|
||||
```bash
|
||||
docker exec -it {db_container_name_or_id} pg_dumpall -U {postgres_user} > databases_backup.sql
|
||||
```
|
||||
|
||||
To restore from backup:
|
||||
لاستعادة النسخة الاحتياطية:
|
||||
|
||||
```bash
|
||||
cat databases_backup.sql | docker exec -i {db_container_name_or_id} psql -U {postgres_user}
|
||||
```
|
||||
|
||||
If you use Docker Compose, follow these steps:
|
||||
إذا كنت تستخدم Docker Compose، اتبع الخطوات التالية:
|
||||
|
||||
1. Stop Twenty: `docker compose down`
|
||||
2. Change the `TAG` value in the `.env` file next to your `docker-compose.yml`
|
||||
3. Start Twenty: `docker compose up -d`
|
||||
1. أوقف Twenty: `docker compose down`
|
||||
2. غيّر قيمة `TAG` في ملف `.env` الموجود بجانب ملف `docker-compose.yml`
|
||||
3. ابدأ تشغيل Twenty: `docker compose up -d`
|
||||
|
||||
The server runs all required upgrade migrations automatically on startup. No manual command is needed.
|
||||
يقوم الخادم بتشغيل جميع عمليات ترحيل الترقية المطلوبة تلقائيًا عند بدء التشغيل. لا حاجة إلى أي أمر يدوي.
|
||||
|
||||
## Cross-version upgrades (v1.22+)
|
||||
## الترقيات عبر الإصدارات (v1.22+)
|
||||
|
||||
Starting from **v1.22**, Twenty supports cross-version upgrades. You can jump directly from any supported version to the latest release without stepping through each intermediate version.
|
||||
بدءًا من **v1.22**، يدعم Twenty الترقيات عبر الإصدارات. يمكنك الانتقال مباشرةً من أي إصدار مدعوم إلى أحدث إصدار دون المرور بكل إصدار وسيط.
|
||||
|
||||
For example, upgrading from v1.22 straight to v2.0 is fully supported.
|
||||
على سبيل المثال، الترقية من v1.22 مباشرةً إلى v2.0 مدعومة بالكامل.
|
||||
|
||||
## Checking upgrade status
|
||||
## التحقق من حالة الترقية
|
||||
|
||||
The `upgrade:status` command lets you inspect the current state of your instance and workspace migrations. It is useful for debugging upgrade issues or when filing a support request.
|
||||
يتيح لك الأمر `upgrade:status` فحص الحالة الحالية لمثيلك وعمليات ترحيل مساحات العمل. يكون مفيدًا لاستكشاف مشكلات الترقية وإصلاحها أو عند تقديم طلب دعم.
|
||||
|
||||
Run it from the server container:
|
||||
قم بتشغيله من حاوية الخادم:
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status
|
||||
@@ -68,23 +68,23 @@ Summary
|
||||
|
||||
### خيارات
|
||||
|
||||
| Flag | الوصف |
|
||||
| ------------------------- | ---------------------------------------------------------------- |
|
||||
| `-w, --workspace-id <id>` | Filter to a specific workspace. Can be passed multiple times. |
|
||||
| `-f, --failed-only` | Hide up-to-date workspaces, only show behind and failed entries. |
|
||||
| خيار | الوصف |
|
||||
| ------------------------- | ----------------------------------------------------------- |
|
||||
| `-w, --workspace-id <id>` | لتصفية حسب مساحة عمل معيّنة. يمكن تمريره عدة مرات. |
|
||||
| `-f, --failed-only` | إخفاء مساحات العمل المحدَّثة، وعرض المتأخرة أو الفاشلة فقط. |
|
||||
|
||||
## استكشاف الأخطاء وإصلاحها
|
||||
|
||||
If the upgrade fails on some workspaces, the server will not advance past the failing step. Restarting the server (`docker compose up -d`) will retry the upgrade from where it left off.
|
||||
إذا فشلت الترقية في بعض مساحات العمل، فلن يتجاوز الخادم الخطوة الفاشلة. إعادة تشغيل الخادم (`docker compose up -d`) ستعيد محاولة الترقية من حيث توقفت.
|
||||
|
||||
To quickly identify problems, run:
|
||||
لتحديد المشكلات بسرعة، قم بتشغيل:
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status --failed-only
|
||||
```
|
||||
|
||||
This shows only workspaces that are behind or have failed, along with the error message for each failure.
|
||||
يعرض هذا فقط مساحات العمل المتأخرة أو التي فشلت، مع رسالة الخطأ لكل حالة فشل.
|
||||
|
||||
## Before v1.22
|
||||
## قبل v1.22
|
||||
|
||||
If your instance is older than v1.22, you must upgrade incrementally through each major tagged version (v1.6 to v1.7, then v1.7 to v1.8, and so on) until you reach v1.22. From there, you can jump directly to the latest version.
|
||||
إذا كان مثيلك أقدم من v1.22، فيجب عليك الترقية تدريجيًا عبر كل إصدار رئيسي موسوم (من v1.6 إلى v1.7، ثم من v1.7 إلى v1.8، وهكذا) حتى تصل إلى v1.22. ومن هناك، يمكنك الانتقال مباشرةً إلى أحدث إصدار.
|
||||
|
||||
@@ -5,37 +5,37 @@ icon: arrow-up-right-dots
|
||||
|
||||
## Obecné pokyny
|
||||
|
||||
**Always back up your database before starting the upgrade process** by running:
|
||||
**Před zahájením procesu aktualizace vždy zálohujte svou databázi** spuštěním:
|
||||
|
||||
```bash
|
||||
docker exec -it {db_container_name_or_id} pg_dumpall -U {postgres_user} > databases_backup.sql
|
||||
```
|
||||
|
||||
To restore from backup:
|
||||
Pro obnovení ze zálohy:
|
||||
|
||||
```bash
|
||||
cat databases_backup.sql | docker exec -i {db_container_name_or_id} psql -U {postgres_user}
|
||||
```
|
||||
|
||||
If you use Docker Compose, follow these steps:
|
||||
Pokud používáte Docker Compose, postupujte takto:
|
||||
|
||||
1. Stop Twenty: `docker compose down`
|
||||
2. Change the `TAG` value in the `.env` file next to your `docker-compose.yml`
|
||||
3. Start Twenty: `docker compose up -d`
|
||||
1. Zastavte Twenty: `docker compose down`
|
||||
2. Změňte hodnotu `TAG` v souboru `.env` vedle `docker-compose.yml`
|
||||
3. Spusťte Twenty: `docker compose up -d`
|
||||
|
||||
The server runs all required upgrade migrations automatically on startup. No manual command is needed.
|
||||
Server při startu automaticky spustí všechny požadované migrační kroky upgradu. Není potřeba žádný ruční příkaz.
|
||||
|
||||
## Cross-version upgrades (v1.22+)
|
||||
## Upgrade napříč verzemi (v1.22+)
|
||||
|
||||
Starting from **v1.22**, Twenty supports cross-version upgrades. You can jump directly from any supported version to the latest release without stepping through each intermediate version.
|
||||
Počínaje **v1.22** podporuje Twenty upgrade napříč verzemi. Můžete přejít přímo z jakékoli podporované verze na nejnovější vydání, aniž byste museli procházet každou meziverzí.
|
||||
|
||||
For example, upgrading from v1.22 straight to v2.0 is fully supported.
|
||||
Například přechod z v1.22 přímo na v2.0 je plně podporován.
|
||||
|
||||
## Checking upgrade status
|
||||
## Kontrola stavu upgradu
|
||||
|
||||
The `upgrade:status` command lets you inspect the current state of your instance and workspace migrations. It is useful for debugging upgrade issues or when filing a support request.
|
||||
Příkaz `upgrade:status` vám umožní zkontrolovat aktuální stav vaší instance a migrací pracovních prostorů. Je užitečný pro ladění problémů s upgradem nebo při podávání požadavku na podporu.
|
||||
|
||||
Run it from the server container:
|
||||
Spusťte jej z kontejneru serveru:
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status
|
||||
@@ -68,23 +68,23 @@ Summary
|
||||
|
||||
### Možnosti
|
||||
|
||||
| Flag | Popis |
|
||||
| ------------------------- | ---------------------------------------------------------------- |
|
||||
| `-w, --workspace-id <id>` | Filter to a specific workspace. Can be passed multiple times. |
|
||||
| `-f, --failed-only` | Hide up-to-date workspaces, only show behind and failed entries. |
|
||||
| Přepínač | Popis |
|
||||
| ------------------------- | ------------------------------------------------------------------------------------ |
|
||||
| `-w, --workspace-id <id>` | Omezí se na konkrétní pracovní prostor. Lze zadat vícekrát. |
|
||||
| `-f, --failed-only` | Skryje aktuální pracovní prostory; zobrazí pouze ty, které jsou pozadu, a neúspěšné. |
|
||||
|
||||
## Řešení potíží
|
||||
|
||||
If the upgrade fails on some workspaces, the server will not advance past the failing step. Restarting the server (`docker compose up -d`) will retry the upgrade from where it left off.
|
||||
Pokud upgrade selže u některých pracovních prostorů, server nepokročí za chybující krok. Restartování serveru (`docker compose up -d`) zkusí upgrade znovu od místa, kde se zastavil.
|
||||
|
||||
To quickly identify problems, run:
|
||||
Pro rychlou identifikaci problémů spusťte:
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status --failed-only
|
||||
```
|
||||
|
||||
This shows only workspaces that are behind or have failed, along with the error message for each failure.
|
||||
Tímto se zobrazí pouze pracovní prostory, které jsou pozadu nebo selhaly, spolu s chybovou zprávou pro každé selhání.
|
||||
|
||||
## Before v1.22
|
||||
## Před v1.22
|
||||
|
||||
If your instance is older than v1.22, you must upgrade incrementally through each major tagged version (v1.6 to v1.7, then v1.7 to v1.8, and so on) until you reach v1.22. From there, you can jump directly to the latest version.
|
||||
Pokud je vaše instance starší než v1.22, musíte upgradovat postupně přes každou hlavní označenou verzi (z v1.6 na v1.7, poté z v1.7 na v1.8 atd.), dokud nedosáhnete v1.22. Odtud můžete přejít přímo na nejnovější verzi.
|
||||
|
||||
@@ -5,37 +5,37 @@ icon: arrow-up-right-dots
|
||||
|
||||
## Allgemeine Richtlinien
|
||||
|
||||
**Always back up your database before starting the upgrade process** by running:
|
||||
**Sichern Sie Ihre Datenbank immer, bevor Sie den Upgrade-Vorgang starten**, indem Sie Folgendes ausführen:
|
||||
|
||||
```bash
|
||||
docker exec -it {db_container_name_or_id} pg_dumpall -U {postgres_user} > databases_backup.sql
|
||||
```
|
||||
|
||||
To restore from backup:
|
||||
Aus Sicherung wiederherstellen:
|
||||
|
||||
```bash
|
||||
cat databases_backup.sql | docker exec -i {db_container_name_or_id} psql -U {postgres_user}
|
||||
```
|
||||
|
||||
If you use Docker Compose, follow these steps:
|
||||
Wenn Sie Docker Compose verwenden, befolgen Sie diese Schritte:
|
||||
|
||||
1. Stop Twenty: `docker compose down`
|
||||
2. Change the `TAG` value in the `.env` file next to your `docker-compose.yml`
|
||||
3. Start Twenty: `docker compose up -d`
|
||||
1. Twenty stoppen: `docker compose down`
|
||||
2. Ändern Sie den Wert von `TAG` in der Datei `.env` neben Ihrer `docker-compose.yml`
|
||||
3. Twenty starten: `docker compose up -d`
|
||||
|
||||
The server runs all required upgrade migrations automatically on startup. No manual command is needed.
|
||||
Der Server führt beim Start alle erforderlichen Upgrade-Migrationen automatisch aus. Kein manueller Befehl erforderlich.
|
||||
|
||||
## Cross-version upgrades (v1.22+)
|
||||
## Versionsübergreifende Upgrades (v1.22+)
|
||||
|
||||
Starting from **v1.22**, Twenty supports cross-version upgrades. You can jump directly from any supported version to the latest release without stepping through each intermediate version.
|
||||
Ab **v1.22** unterstützt Twenty versionsübergreifende Upgrades. Sie können direkt von jeder unterstützten Version auf die neueste Version wechseln, ohne jede Zwischenversion durchlaufen zu müssen.
|
||||
|
||||
For example, upgrading from v1.22 straight to v2.0 is fully supported.
|
||||
Zum Beispiel wird ein Upgrade direkt von v1.22 auf v2.0 vollständig unterstützt.
|
||||
|
||||
## Checking upgrade status
|
||||
## Upgrade-Status prüfen
|
||||
|
||||
The `upgrade:status` command lets you inspect the current state of your instance and workspace migrations. It is useful for debugging upgrade issues or when filing a support request.
|
||||
Mit dem Befehl `upgrade:status` können Sie den aktuellen Status Ihrer Instanz und der Workspace-Migrationen prüfen. Er ist nützlich zum Debuggen von Upgrade-Problemen oder beim Erstellen einer Support-Anfrage.
|
||||
|
||||
Run it from the server container:
|
||||
Führen Sie ihn im Server-Container aus:
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status
|
||||
@@ -68,23 +68,23 @@ Summary
|
||||
|
||||
### Optionen
|
||||
|
||||
| Flag | Beschreibung |
|
||||
| ------------------------- | ---------------------------------------------------------------- |
|
||||
| `-w, --workspace-id <id>` | Filter to a specific workspace. Can be passed multiple times. |
|
||||
| `-f, --failed-only` | Hide up-to-date workspaces, only show behind and failed entries. |
|
||||
| Flag | Beschreibung |
|
||||
| ------------------------- | --------------------------------------------------------------------------------------------------------- |
|
||||
| `-w, --workspace-id <id>` | Auf einen bestimmten Workspace filtern. Kann mehrfach übergeben werden. |
|
||||
| `-f, --failed-only` | Workspaces auf dem neuesten Stand ausblenden, nur zurückliegende und fehlgeschlagene Workspaces anzeigen. |
|
||||
|
||||
## Fehlerbehebung
|
||||
|
||||
If the upgrade fails on some workspaces, the server will not advance past the failing step. Restarting the server (`docker compose up -d`) will retry the upgrade from where it left off.
|
||||
Wenn das Upgrade in einigen Workspaces fehlschlägt, wird der Server nicht über den fehlschlagenden Schritt hinaus fortfahren. Ein Neustart des Servers (`docker compose up -d`) führt das Upgrade ab der zuletzt erreichten Stelle erneut aus.
|
||||
|
||||
To quickly identify problems, run:
|
||||
Um Probleme schnell zu identifizieren, führen Sie Folgendes aus:
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status --failed-only
|
||||
```
|
||||
|
||||
This shows only workspaces that are behind or have failed, along with the error message for each failure.
|
||||
Dies zeigt nur Workspaces, die zurückliegen oder fehlgeschlagen sind, zusammen mit der Fehlermeldung für jeden Fehlschlag.
|
||||
|
||||
## Before v1.22
|
||||
## Vor v1.22
|
||||
|
||||
If your instance is older than v1.22, you must upgrade incrementally through each major tagged version (v1.6 to v1.7, then v1.7 to v1.8, and so on) until you reach v1.22. From there, you can jump directly to the latest version.
|
||||
Wenn Ihre Instanz älter als v1.22 ist, müssen Sie schrittweise über jede größere getaggte Version ein Upgrade durchführen (von v1.6 auf v1.7, dann von v1.7 auf v1.8 usw.), bis Sie v1.22 erreichen. Danach können Sie direkt auf die neueste Version wechseln.
|
||||
|
||||
@@ -5,37 +5,37 @@ icon: arrow-up-right-dots
|
||||
|
||||
## Linee guida generali
|
||||
|
||||
**Always back up your database before starting the upgrade process** by running:
|
||||
**Esegui sempre un backup del database prima di iniziare la procedura di aggiornamento** eseguendo:
|
||||
|
||||
```bash
|
||||
docker exec -it {db_container_name_or_id} pg_dumpall -U {postgres_user} > databases_backup.sql
|
||||
```
|
||||
|
||||
To restore from backup:
|
||||
Per ripristinare dal backup:
|
||||
|
||||
```bash
|
||||
cat databases_backup.sql | docker exec -i {db_container_name_or_id} psql -U {postgres_user}
|
||||
```
|
||||
|
||||
If you use Docker Compose, follow these steps:
|
||||
Se utilizzi Docker Compose, segui questi passaggi:
|
||||
|
||||
1. Stop Twenty: `docker compose down`
|
||||
2. Change the `TAG` value in the `.env` file next to your `docker-compose.yml`
|
||||
3. Start Twenty: `docker compose up -d`
|
||||
1. Arresta Twenty: `docker compose down`
|
||||
2. Modifica il valore di `TAG` nel file `.env` nella stessa directory di `docker-compose.yml`
|
||||
3. Avvia Twenty: `docker compose up -d`
|
||||
|
||||
The server runs all required upgrade migrations automatically on startup. No manual command is needed.
|
||||
All'avvio, il server esegue automaticamente tutte le migrazioni di aggiornamento necessarie. Non è necessario alcun comando manuale.
|
||||
|
||||
## Cross-version upgrades (v1.22+)
|
||||
## Aggiornamenti tra versioni (v1.22+)
|
||||
|
||||
Starting from **v1.22**, Twenty supports cross-version upgrades. You can jump directly from any supported version to the latest release without stepping through each intermediate version.
|
||||
A partire da **v1.22**, Twenty supporta gli aggiornamenti tra versioni. Puoi passare direttamente da qualsiasi versione supportata all'ultima versione senza dover attraversare ogni versione intermedia.
|
||||
|
||||
For example, upgrading from v1.22 straight to v2.0 is fully supported.
|
||||
Ad esempio, l'aggiornamento da v1.22 direttamente a v2.0 è pienamente supportato.
|
||||
|
||||
## Checking upgrade status
|
||||
## Verifica dello stato dell'aggiornamento
|
||||
|
||||
The `upgrade:status` command lets you inspect the current state of your instance and workspace migrations. It is useful for debugging upgrade issues or when filing a support request.
|
||||
Il comando `upgrade:status` consente di ispezionare lo stato corrente della tua istanza e delle migrazioni degli spazi di lavoro. È utile per eseguire il debug di problemi di aggiornamento o quando si apre una richiesta di assistenza.
|
||||
|
||||
Run it from the server container:
|
||||
Eseguilo dal container del server:
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status
|
||||
@@ -68,23 +68,23 @@ Summary
|
||||
|
||||
### Opzioni
|
||||
|
||||
| Flag | Descrizione |
|
||||
| ------------------------- | ---------------------------------------------------------------- |
|
||||
| `-w, --workspace-id <id>` | Filter to a specific workspace. Can be passed multiple times. |
|
||||
| `-f, --failed-only` | Hide up-to-date workspaces, only show behind and failed entries. |
|
||||
| Opzione | Descrizione |
|
||||
| ------------------------- | -------------------------------------------------------------------------------------------- |
|
||||
| `-w, --workspace-id <id>` | Filtra per uno specifico spazio di lavoro. Può essere passato più volte. |
|
||||
| `-f, --failed-only` | Nasconde gli spazi di lavoro aggiornati; mostra solo quelli arretrati e quelli non riusciti. |
|
||||
|
||||
## Risoluzione dei problemi
|
||||
|
||||
If the upgrade fails on some workspaces, the server will not advance past the failing step. Restarting the server (`docker compose up -d`) will retry the upgrade from where it left off.
|
||||
Se l'aggiornamento non riesce su alcuni spazi di lavoro, il server non proseguirà oltre il passaggio in cui si è verificato l'errore. Riavviando il server (`docker compose up -d`), l'aggiornamento verrà riprovato dal punto in cui era stato interrotto.
|
||||
|
||||
To quickly identify problems, run:
|
||||
Per identificare rapidamente i problemi, esegui:
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status --failed-only
|
||||
```
|
||||
|
||||
This shows only workspaces that are behind or have failed, along with the error message for each failure.
|
||||
Mostra solo gli spazi di lavoro arretrati o non riusciti, insieme al messaggio di errore per ciascun errore.
|
||||
|
||||
## Before v1.22
|
||||
## Prima della v1.22
|
||||
|
||||
If your instance is older than v1.22, you must upgrade incrementally through each major tagged version (v1.6 to v1.7, then v1.7 to v1.8, and so on) until you reach v1.22. From there, you can jump directly to the latest version.
|
||||
Se la tua istanza è precedente alla v1.22, devi eseguire l'aggiornamento in modo incrementale attraverso ogni versione maggiore contrassegnata (da v1.6 a v1.7, poi da v1.7 a v1.8 e così via) fino a raggiungere la v1.22. Da lì, puoi passare direttamente all'ultima versione.
|
||||
|
||||
@@ -5,37 +5,37 @@ icon: arrow-up-right-dots
|
||||
|
||||
## Diretrizes gerais
|
||||
|
||||
**Always back up your database before starting the upgrade process** by running:
|
||||
**Sempre faça backup do seu banco de dados antes de iniciar o processo de atualização** executando:
|
||||
|
||||
```bash
|
||||
docker exec -it {db_container_name_or_id} pg_dumpall -U {postgres_user} > databases_backup.sql
|
||||
```
|
||||
|
||||
To restore from backup:
|
||||
Para restaurar a partir de um backup:
|
||||
|
||||
```bash
|
||||
cat databases_backup.sql | docker exec -i {db_container_name_or_id} psql -U {postgres_user}
|
||||
```
|
||||
|
||||
If you use Docker Compose, follow these steps:
|
||||
Se você usa o Docker Compose, siga estas etapas:
|
||||
|
||||
1. Stop Twenty: `docker compose down`
|
||||
2. Change the `TAG` value in the `.env` file next to your `docker-compose.yml`
|
||||
3. Start Twenty: `docker compose up -d`
|
||||
1. Pare o Twenty: `docker compose down`
|
||||
2. Altere o valor de `TAG` no arquivo `.env` que está no mesmo diretório do seu `docker-compose.yml`
|
||||
3. Inicie o Twenty: `docker compose up -d`
|
||||
|
||||
The server runs all required upgrade migrations automatically on startup. No manual command is needed.
|
||||
O servidor executa automaticamente todas as migrações de atualização necessárias na inicialização. Nenhum comando manual é necessário.
|
||||
|
||||
## Cross-version upgrades (v1.22+)
|
||||
## Atualizações entre versões (v1.22+)
|
||||
|
||||
Starting from **v1.22**, Twenty supports cross-version upgrades. You can jump directly from any supported version to the latest release without stepping through each intermediate version.
|
||||
A partir da **v1.22**, o Twenty oferece suporte a atualizações entre versões. Você pode pular diretamente de qualquer versão compatível para a versão mais recente sem passar por cada versão intermediária.
|
||||
|
||||
For example, upgrading from v1.22 straight to v2.0 is fully supported.
|
||||
Por exemplo, a atualização da v1.22 diretamente para a v2.0 é totalmente suportada.
|
||||
|
||||
## Checking upgrade status
|
||||
## Verificando o status da atualização
|
||||
|
||||
The `upgrade:status` command lets you inspect the current state of your instance and workspace migrations. It is useful for debugging upgrade issues or when filing a support request.
|
||||
O comando `upgrade:status` permite inspecionar o estado atual da sua instância e das migrações dos espaços de trabalho. É útil para depurar problemas de atualização ou ao abrir uma solicitação de suporte.
|
||||
|
||||
Run it from the server container:
|
||||
Execute-o a partir do contêiner do servidor:
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status
|
||||
@@ -68,23 +68,23 @@ Summary
|
||||
|
||||
### Opções
|
||||
|
||||
| Flag | Descrição |
|
||||
| ------------------------- | ---------------------------------------------------------------- |
|
||||
| `-w, --workspace-id <id>` | Filter to a specific workspace. Can be passed multiple times. |
|
||||
| `-f, --failed-only` | Hide up-to-date workspaces, only show behind and failed entries. |
|
||||
| Opção | Descrição |
|
||||
| ------------------------- | ---------------------------------------------------------------------------------------------------- |
|
||||
| `-w, --workspace-id <id>` | Restringe a um espaço de trabalho específico. Pode ser passada várias vezes. |
|
||||
| `-f, --failed-only` | Oculta os espaços de trabalho atualizados; mostra apenas os que estão desatualizados e os com falha. |
|
||||
|
||||
## Resolução de Problemas
|
||||
|
||||
If the upgrade fails on some workspaces, the server will not advance past the failing step. Restarting the server (`docker compose up -d`) will retry the upgrade from where it left off.
|
||||
Se a atualização falhar em alguns espaços de trabalho, o servidor não avançará além da etapa com falha. Reiniciar o servidor (`docker compose up -d`) tentará novamente a atualização a partir de onde parou.
|
||||
|
||||
To quickly identify problems, run:
|
||||
Para identificar rapidamente os problemas, execute:
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status --failed-only
|
||||
```
|
||||
|
||||
This shows only workspaces that are behind or have failed, along with the error message for each failure.
|
||||
Isso mostra apenas os espaços de trabalho que estão desatualizados ou com falha, juntamente com a mensagem de erro de cada falha.
|
||||
|
||||
## Before v1.22
|
||||
## Antes da v1.22
|
||||
|
||||
If your instance is older than v1.22, you must upgrade incrementally through each major tagged version (v1.6 to v1.7, then v1.7 to v1.8, and so on) until you reach v1.22. From there, you can jump directly to the latest version.
|
||||
Se a sua instância for anterior à v1.22, você deve atualizar incrementalmente por cada versão principal marcada (da v1.6 para a v1.7, depois da v1.7 para a v1.8 e assim por diante) até chegar à v1.22. A partir daí, você pode pular diretamente para a versão mais recente.
|
||||
|
||||
@@ -5,7 +5,7 @@ icon: robot
|
||||
---
|
||||
|
||||
<Warning>
|
||||
Skills and agents are currently in alpha. Функция работает, но продолжает развиваться.
|
||||
Навыки и агенты сейчас проходят альфа-тестирование. Функция работает, но продолжает развиваться.
|
||||
</Warning>
|
||||
|
||||
Приложения могут определять возможности ИИ, которые находятся внутри рабочего пространства — повторно используемые инструкции для навыков и агенты с настраиваемыми системными подсказками.
|
||||
|
||||
@@ -5,7 +5,7 @@ icon: robot
|
||||
---
|
||||
|
||||
<Warning>
|
||||
Skills and agents are currently in alpha. Özellik işlevsel ancak hâlâ gelişmekte.
|
||||
Beceriler ve ajanlar şu anda alfa aşamasında. Özellik işlevsel ancak hâlâ gelişmekte.
|
||||
</Warning>
|
||||
|
||||
Uygulamalar, çalışma alanı içinde yer alan yapay zekâ yeteneklerini — yeniden kullanılabilir yetenek yönergeleri ve özel sistem istemlerine sahip ajanları — tanımlayabilir.
|
||||
|
||||
@@ -5,37 +5,37 @@ icon: arrow-up-right-dots
|
||||
|
||||
## 通用指南
|
||||
|
||||
**Always back up your database before starting the upgrade process** by running:
|
||||
**在开始升级流程之前务必备份数据库**，运行：
|
||||
|
||||
```bash
|
||||
docker exec -it {db_container_name_or_id} pg_dumpall -U {postgres_user} > databases_backup.sql
|
||||
```
|
||||
|
||||
To restore from backup:
|
||||
从备份恢复：
|
||||
|
||||
```bash
|
||||
cat databases_backup.sql | docker exec -i {db_container_name_or_id} psql -U {postgres_user}
|
||||
```
|
||||
|
||||
If you use Docker Compose, follow these steps:
|
||||
如果您使用 Docker Compose，请按照以下步骤操作：
|
||||
|
||||
1. Stop Twenty: `docker compose down`
|
||||
2. Change the `TAG` value in the `.env` file next to your `docker-compose.yml`
|
||||
3. Start Twenty: `docker compose up -d`
|
||||
1. 停止 Twenty：`docker compose down`
|
||||
2. 在与 `docker-compose.yml` 同目录的 `.env` 文件中更改 `TAG` 值
|
||||
3. 启动 Twenty：`docker compose up -d`
|
||||
|
||||
The server runs all required upgrade migrations automatically on startup. No manual command is needed.
|
||||
服务器在启动时会自动运行所有所需的升级迁移。 无需手动执行任何命令。
|
||||
|
||||
## Cross-version upgrades (v1.22+)
|
||||
## 跨版本升级（v1.22+）
|
||||
|
||||
Starting from **v1.22**, Twenty supports cross-version upgrades. You can jump directly from any supported version to the latest release without stepping through each intermediate version.
|
||||
自 **v1.22** 起，Twenty 支持跨版本升级。 您可以从任意受支持的版本直接跳到最新版本，而无需逐一经过每个中间版本。
|
||||
|
||||
For example, upgrading from v1.22 straight to v2.0 is fully supported.
|
||||
例如，从 v1.22 直接升级到 v2.0 完全受支持。
|
||||
|
||||
## Checking upgrade status
|
||||
## 检查升级状态
|
||||
|
||||
The `upgrade:status` command lets you inspect the current state of your instance and workspace migrations. It is useful for debugging upgrade issues or when filing a support request.
|
||||
`upgrade:status` 命令可用于查看您的实例和工作区迁移的当前状态。 这在调试升级问题或提交支持请求时非常有用。
|
||||
|
||||
Run it from the server container:
|
||||
在服务器容器中运行：
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status
|
||||
@@ -68,23 +68,23 @@ Summary
|
||||
|
||||
### 选项
|
||||
|
||||
| Flag | 描述 |
|
||||
| ------------------------- | ---------------------------------------------------------------- |
|
||||
| `-w, --workspace-id <id>` | Filter to a specific workspace. Can be passed multiple times. |
|
||||
| `-f, --failed-only` | Hide up-to-date workspaces, only show behind and failed entries. |
|
||||
| 标志 | 描述 |
|
||||
| ------------------------- | ----------------------- |
|
||||
| `-w, --workspace-id <id>` | 筛选特定工作区。 可多次传递。 |
|
||||
| `-f, --failed-only` | 隐藏已是最新的工作区，仅显示落后和失败的条目。 |
|
||||
|
||||
## 故障排除
|
||||
|
||||
If the upgrade fails on some workspaces, the server will not advance past the failing step. Restarting the server (`docker compose up -d`) will retry the upgrade from where it left off.
|
||||
如果某些工作区的升级失败，服务器将不会越过失败的步骤继续进行。 重启服务器（`docker compose up -d`）将从中断处重试升级。
|
||||
|
||||
To quickly identify problems, run:
|
||||
要快速定位问题，运行：
|
||||
|
||||
```bash
|
||||
docker exec -it {server_container_name_or_id} yarn command:prod upgrade:status --failed-only
|
||||
```
|
||||
|
||||
This shows only workspaces that are behind or have failed, along with the error message for each failure.
|
||||
这将仅显示落后或失败的工作区，并附上每个失败的错误信息。
|
||||
|
||||
## Before v1.22
|
||||
## v1.22 之前
|
||||
|
||||
If your instance is older than v1.22, you must upgrade incrementally through each major tagged version (v1.6 to v1.7, then v1.7 to v1.8, and so on) until you reach v1.22. From there, you can jump directly to the latest version.
|
||||
如果您的实例早于 v1.22，您必须按顺序逐步升级经过每个主要标记版本（从 v1.6 到 v1.7，再从 v1.7 到 v1.8，依此类推），直到达到 v1.22。 届时，您可以直接跳到最新版本。
|
||||
|
||||
Reference in New Issue
Block a user