The open alternative to Salesforce, designed for AI.
TypeScript crmcrm-systemcustomergood-first-issuegraphqlhacktoberfestjavascriptmarketingmonoreponestjsopen-sourcepostgresqlreactreactjssalestypescriptweb
i18n - docs translations (#20248)
github-actions[bot]8c2885f9ed2d
diff --git a/packages/twenty-docs/l/de/developers/extend/apps/getting-started.mdx b/packages/twenty-docs/l/de/developers/extend/apps/getting-started.mdxindex 0b94b01f2f2..47d5345bbef 100644--- a/packages/twenty-docs/l/de/developers/extend/apps/getting-started.mdx+++ b/packages/twenty-docs/l/de/developers/extend/apps/getting-started.mdx@@ -88,7 +88,7 @@ yarn twenty dev --verbose```<Warning>-Der Dev-Modus ist nur auf Twenty-Instanzen verfügbar, die im Entwicklungsmodus laufen (`NODE_ENV=development`). Produktionsinstanzen lehnen Dev-Synchronisierungsanfragen ab. Use `yarn twenty deploy` followed by `yarn twenty install` to publish and install on production servers — `deploy` publishes to the application registry, while `install` installs it on a given workspace. See [Publishing Apps](/l/de/developers/extend/apps/publishing) for details.+Der Dev-Modus ist nur auf Twenty-Instanzen verfügbar, die im Entwicklungsmodus laufen (`NODE_ENV=development`). Produktionsinstanzen lehnen Dev-Synchronisierungsanfragen ab. Verwenden Sie `yarn twenty deploy`, gefolgt von `yarn twenty install`, um auf Produktionsservern zu veröffentlichen und zu installieren — `deploy` veröffentlicht im Anwendungsregister, während `install` es in einem angegebenen Arbeitsbereich installiert. Details finden Sie unter [Apps veröffentlichen](/l/de/developers/extend/apps/publishing).</Warning><div style={{textAlign: 'center'}}>diff --git a/packages/twenty-docs/l/pt/developers/extend/apps/getting-started.mdx b/packages/twenty-docs/l/pt/developers/extend/apps/getting-started.mdxindex 63533932815..8add22f5fab 100644--- a/packages/twenty-docs/l/pt/developers/extend/apps/getting-started.mdx+++ b/packages/twenty-docs/l/pt/developers/extend/apps/getting-started.mdx@@ -88,7 +88,7 @@ yarn twenty dev --verbose```<Warning>-O modo de desenvolvimento só está disponível em instâncias do Twenty em modo de desenvolvimento (`NODE_ENV=development`). Instâncias de produção rejeitam solicitações de sincronização de desenvolvimento. Use `yarn twenty deploy` followed by `yarn twenty install` to publish and install on production servers — `deploy` publishes to the application registry, while `install` installs it on a given workspace. See [Publishing Apps](/l/pt/developers/extend/apps/publishing) for details.+O modo de desenvolvimento só está disponível em instâncias do Twenty em modo de desenvolvimento (`NODE_ENV=development`). Instâncias de produção rejeitam solicitações de sincronização de desenvolvimento. Use `yarn twenty deploy` seguido de `yarn twenty install` para publicar e instalar em servidores de produção — `deploy` publica no registro de aplicativos, enquanto `install` o instala em um determinado workspace. Veja [Publicação de aplicativos](/l/pt/developers/extend/apps/publishing) para detalhes.</Warning><div style={{textAlign: 'center'}}>diff --git a/packages/twenty-docs/l/ru/developers/extend/apps/getting-started.mdx b/packages/twenty-docs/l/ru/developers/extend/apps/getting-started.mdxindex 833e42a42c5..bae43f7e4c7 100644--- a/packages/twenty-docs/l/ru/developers/extend/apps/getting-started.mdx+++ b/packages/twenty-docs/l/ru/developers/extend/apps/getting-started.mdx@@ -88,7 +88,7 @@ yarn twenty dev --verbose```<Warning>-Режим разработки доступен только на экземплярах Twenty, запущенных в режиме разработки (`NODE_ENV=development`). Экземпляры в продакшене отклоняют запросы синхронизации из режима разработки. Use `yarn twenty deploy` followed by `yarn twenty install` to publish and install on production servers — `deploy` publishes to the application registry, while `install` installs it on a given workspace. See [Publishing Apps](/l/ru/developers/extend/apps/publishing) for details.+Режим разработки доступен только на экземплярах Twenty, запущенных в режиме разработки (`NODE_ENV=development`). Экземпляры в продакшене отклоняют запросы синхронизации из режима разработки. Используйте `yarn twenty deploy`, а затем `yarn twenty install`, чтобы выполнить публикацию и установку на продакшн-серверах — `deploy` публикует в реестр приложений, а `install` устанавливает его в указанное рабочее пространство. См. [Публикация приложений](/l/ru/developers/extend/apps/publishing) для подробностей.</Warning><div style={{textAlign: 'center'}}>diff --git a/packages/twenty-docs/l/ru/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/ru/developers/extend/apps/publishing.mdxindex d0a1d3604c0..80c3d6d167b 100644--- a/packages/twenty-docs/l/ru/developers/extend/apps/publishing.mdx+++ b/packages/twenty-docs/l/ru/developers/extend/apps/publishing.mdx@@ -77,9 +77,9 @@ When updating an already deployed tarball app, the server requires the `version`{/* TODO: add screenshot of the Upgrade button */}-### Server version compatibility+### Совместимость версий сервера-If your app uses a feature introduced in a specific Twenty server version (for example, OAuth providers added in v2.3.0), you should declare the minimum server version your app requires using the `engines.twenty` field in `package.json`:+Если ваше приложение использует функцию, появившуюся в конкретной версии сервера Twenty (например, провайдеры OAuth, добавленные в v2.3.0), следует объявить минимальную требуемую версию сервера с помощью поля `engines.twenty` в `package.json`:```json filename="package.json"{@@ -92,22 +92,22 @@ If your app uses a feature introduced in a specific Twenty server version (for e}```-The value is a standard [semver range](https://github.com/npm/node-semver#ranges). Common patterns:+Значение — это стандартный [диапазон semver](https://github.com/npm/node-semver#ranges). Типовые шаблоны:-| Range | Meaning |-| ---------------------------------- | ------------------------------------------ |-| `>=2.3.0` | Any server from 2.3.0 onward |-| `>=2.3.0 \<3.0.0` | 2.3.0 or later, but below the next major |-| `^2.3.0` | Same as `>=2.3.0 \<3.0.0` |+| Диапазон | Значение |+| ---------------------------------- | -------------------------------------------------- |+| `>=2.3.0` | Любой сервер версии 2.3.0 и новее |+| `>=2.3.0 \<3.0.0` | 2.3.0 или новее, но ниже следующей мажорной версии |+| `^2.3.0` | То же, что и `>=2.3.0 \<3.0.0` |-**What happens at deploy and install time:**+**Что происходит при развёртывании и установке:**-* If `engines.twenty` is set and the target server's version does not satisfy the range, the deploy (tarball upload) or install is rejected with a `SERVER_VERSION_INCOMPATIBLE` error and a message indicating both the required range and the actual server version.-* If `engines.twenty` is **not set**, the app is accepted on any server version (backward-compatible with existing apps).-* If the server has no `APP_VERSION` configured, the check is skipped.+* Если `engines.twenty` задано и версия целевого сервера не удовлетворяет диапазону, развёртывание (загрузка tarball-архива) или установка отклоняются с ошибкой `SERVER_VERSION_INCOMPATIBLE` и сообщением, указывающим как требуемый диапазон, так и фактическую версию сервера.+* Если `engines.twenty` **не задано**, приложение принимается на сервере любой версии (обратная совместимость с существующими приложениями).+* Если на сервере `APP_VERSION` не задано, проверка пропускается.<Note>-The server is the authoritative check — it validates `engines.twenty` on both tarball upload and workspace install. If you deploy a tarball out-of-band or install from the marketplace, the server still enforces compatibility.+Сервер выполняет окончательную проверку — он проверяет `engines.twenty` как при загрузке tarball-архива, так и при установке в рабочем пространстве. Если вы развёртываете tarball вне стандартного процесса или устанавливаете из маркетплейса, сервер всё равно принудительно проверяет совместимость.</Note>## Автоматизированный CI/CD (рабочие процессы, сгенерированные шаблоном)diff --git a/packages/twenty-docs/l/tr/developers/extend/apps/getting-started.mdx b/packages/twenty-docs/l/tr/developers/extend/apps/getting-started.mdxindex db572669bbf..774d1f80f4a 100644--- a/packages/twenty-docs/l/tr/developers/extend/apps/getting-started.mdx+++ b/packages/twenty-docs/l/tr/developers/extend/apps/getting-started.mdx@@ -88,7 +88,7 @@ yarn twenty dev --verbose```<Warning>-Geliştirme modu yalnızca geliştirme ortamında (`NODE_ENV=development`) çalışan Twenty örneklerinde kullanılabilir. Üretim örnekleri geliştirme eşitleme isteklerini reddeder. Use `yarn twenty deploy` followed by `yarn twenty install` to publish and install on production servers — `deploy` publishes to the application registry, while `install` installs it on a given workspace. See [Publishing Apps](/l/tr/developers/extend/apps/publishing) for details.+Geliştirme modu yalnızca geliştirme ortamında (`NODE_ENV=development`) çalışan Twenty örneklerinde kullanılabilir. Üretim örnekleri geliştirme eşitleme isteklerini reddeder. Canlı sunucularda yayımlamak ve yüklemek için önce `yarn twenty deploy`, ardından `yarn twenty install` komutlarını kullanın — `deploy` uygulama kayıt defterine yayımlar, `install` ise bunu belirli bir çalışma alanına yükler. Ayrıntılar için [Uygulamaları Yayımlama](/l/tr/developers/extend/apps/publishing) bölümüne bakın.</Warning><div style={{textAlign: 'center'}}>diff --git a/packages/twenty-docs/l/tr/developers/extend/apps/publishing.mdx b/packages/twenty-docs/l/tr/developers/extend/apps/publishing.mdxindex a78af24feef..67816a9e608 100644--- a/packages/twenty-docs/l/tr/developers/extend/apps/publishing.mdx+++ b/packages/twenty-docs/l/tr/developers/extend/apps/publishing.mdx@@ -77,9 +77,9 @@ Bir güncelleme yayımlamak için:{/* TODO: add screenshot of the Upgrade button */}-### Server version compatibility+### Sunucu sürümü uyumluluğu-If your app uses a feature introduced in a specific Twenty server version (for example, OAuth providers added in v2.3.0), you should declare the minimum server version your app requires using the `engines.twenty` field in `package.json`:+Uygulamanız belirli bir Twenty sunucu sürümünde sunulan bir özelliği kullanıyorsa (örneğin, v2.3.0'da eklenen OAuth sağlayıcıları), uygulamanızın gerektirdiği en düşük sunucu sürümünü `package.json` içindeki `engines.twenty` alanını kullanarak belirtmelisiniz:```json filename="package.json"{@@ -92,22 +92,22 @@ If your app uses a feature introduced in a specific Twenty server version (for e}```-The value is a standard [semver range](https://github.com/npm/node-semver#ranges). Common patterns:+Değer, standart bir [semver aralığı](https://github.com/npm/node-semver#ranges)dır. Yaygın Kalıplar:-| Range | Meaning |-| ---------------------------------- | ------------------------------------------ |-| `>=2.3.0` | Any server from 2.3.0 onward |-| `>=2.3.0 \<3.0.0` | 2.3.0 or later, but below the next major |-| `^2.3.0` | Same as `>=2.3.0 \<3.0.0` |+| Aralık | Anlam |+| ---------------------------------- | --------------------------------------------------------- |+| `>=2.3.0` | 2.3.0'dan itibaren herhangi bir sunucu |+| `>=2.3.0 \<3.0.0` | 2.3.0 veya sonrası, ancak bir sonraki ana sürümün altında |+| `^2.3.0` | `>=2.3.0 \<3.0.0` ile aynı |-**What happens at deploy and install time:**+**Dağıtım ve yükleme sırasında ne olur:**-* If `engines.twenty` is set and the target server's version does not satisfy the range, the deploy (tarball upload) or install is rejected with a `SERVER_VERSION_INCOMPATIBLE` error and a message indicating both the required range and the actual server version.-* If `engines.twenty` is **not set**, the app is accepted on any server version (backward-compatible with existing apps).-* If the server has no `APP_VERSION` configured, the check is skipped.+* `engines.twenty` ayarlanmışsa ve hedef sunucunun sürümü aralığı karşılamıyorsa, dağıtım (tarball yüklemesi) veya yükleme, gerekli aralığı ve gerçek sunucu sürümünü belirten bir mesajla birlikte `SERVER_VERSION_INCOMPATIBLE` hatasıyla reddedilir.+* `engines.twenty` **ayarlı değilse**, uygulama herhangi bir sunucu sürümünde kabul edilir (mevcut uygulamalarla geriye dönük uyumludur).+* Sunucuda `APP_VERSION` yapılandırılmamışsa, denetim atlanır.<Note>-The server is the authoritative check — it validates `engines.twenty` on both tarball upload and workspace install. If you deploy a tarball out-of-band or install from the marketplace, the server still enforces compatibility.+Nihai denetim sunucudadır — hem tarball yüklemesinde hem de çalışma alanı (workspace) kurulumunda `engines.twenty`'yi doğrular. Bir tarball'ı bant dışı dağıtırsanız veya marketplace'ten kurarsanız, sunucu yine de uyumluluğu zorunlu kılar.</Note>## Otomatik CI/CD (hazır şablonlu iş akışları)diff --git a/packages/twenty-docs/l/zh/developers/extend/apps/getting-started.mdx b/packages/twenty-docs/l/zh/developers/extend/apps/getting-started.mdxindex c2f08510f08..39e899e3abb 100644--- a/packages/twenty-docs/l/zh/developers/extend/apps/getting-started.mdx+++ b/packages/twenty-docs/l/zh/developers/extend/apps/getting-started.mdx@@ -88,7 +88,7 @@ yarn twenty dev --verbose```<Warning>-开发模式仅适用于以开发模式运行的 Twenty 实例(`NODE_ENV=development`)。 生产实例会拒绝开发同步请求。 Use `yarn twenty deploy` followed by `yarn twenty install` to publish and install on production servers — `deploy` publishes to the application registry, while `install` installs it on a given workspace. See [Publishing Apps](/l/zh/developers/extend/apps/publishing) for details.+开发模式仅适用于以开发模式运行的 Twenty 实例(`NODE_ENV=development`)。 生产实例会拒绝开发同步请求。 使用 `yarn twenty deploy`,然后执行 `yarn twenty install`,即可在生产服务器上发布并安装 — `deploy` 会发布到应用注册表,而 `install` 会在指定的工作区中进行安装。 详情请参见[发布应用](/l/zh/developers/extend/apps/publishing)。</Warning><div style={{textAlign: 'center'}}>