Files
twenty/packages/twenty-docs/l/de/developers/self-host/self-host.mdx
T
Félix Malfait 7d7f32b243 docs: remove the self-host cloud providers page (#21134)
## What

Removes the community-maintained **"Other methods"** cloud-providers
page from the self-host docs (it covered Kubernetes/Terraform/Coolify
community deployments).

## Changes

- **Deleted** `developers/self-host/capabilities/cloud-providers.mdx`
and its 13 localized copies (ar, cs, de, es, fr, it, ja, ko, pt, ro, ru,
tr, zh).
- **Removed the slug** from `navigation/base-structure.json` (the source
of truth) and regenerated the derived files via the repo's own
generators (`yarn docs:generate`, `yarn docs:generate-paths`):
  - `docs.json` — nav entries dropped for every locale.
- `twenty-shared/.../DocumentationPaths.ts` —
`DEVELOPERS_SELF_HOST_CAPABILITIES_CLOUD_PROVIDERS` constant dropped
(was unused elsewhere).
- **Removed the "Cloud Providers" card** from the `self-host` overview
pages across all locales.
- **Dropped the dangling redirect**
`/developers/self-hosting/cloud-providers` (its destination no longer
exists).
- Cleared the matching entry from the unused `navigation-schema.json`
for consistency.

Net: 68 line deletions across config (pure removal); no insertions.

## Verification

- `grep` confirms **0** remaining references to `cloud-providers`
anywhere in the repo.
- All touched JSON files parse; `oxlint` on twenty-docs reports 0
errors.
- Generators (not hand edits) produced `docs.json` and
`DocumentationPaths.ts`.

> Note: `mintlify broken-links` can't run to completion on this branch
due to a **pre-existing** MDX parse error in the unrelated
`l/ar/.../contribute/contribute.mdx`; the grep above is the equivalent
guarantee that no link points at the removed page.
2026-06-02 11:17:37 +02:00

27 lines
847 B
Plaintext

---
title: Selbsthosting
description: Stellen Sie Twenty auf Ihrer eigenen Infrastruktur bereit und verwalten Sie es.
---
<Frame>
<img src="/images/user-guide/what-is-twenty/20.png" alt="KI" />
</Frame>
## Überblick
Twenty kann auf Ihrer eigenen Infrastruktur im Selbsthosting betrieben werden, sodass Sie die volle Kontrolle über Ihre Daten und Ihre Bereitstellung haben.
## Warum Selbsthosting?
* **Datenhoheit**: Behalten Sie alle CRM-Daten auf Ihren eigenen Servern
* **Compliance**: Erfüllen Sie regulatorische Anforderungen an die Datenresidenz
* **Anpassung**: Voller Zugriff, um die Plattform zu ändern und zu erweitern
## Erste Schritte
<CardGroup cols={2}>
<Card title="Docker Compose" icon="docker" href="/l/de/developers/self-host/capabilities/docker-compose">
Schnelle Einrichtung mit Docker
</Card>
</CardGroup>