github/penpot
1
0
Fork 0
mirror of https://github.com/penpot/penpot.git synced 2026-05-25 01:43:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

📚 Add notice regarding architectural constraints with MCP Server (#9423)

Browse Source
This commit is contained in:
Yamila Moreno 2026-05-12 10:06:13 +02:00 committed by GitHub
parent 11a72abdcd
commit 328efd4e16
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/technical-guide/configuration.md
View File

@ -415,6 +415,12 @@ In a high-availability (HA) scenario, managing the state outside of replicas is
- Valkey: Penpot only needs one Valkey instance to function correctly. Due to the nature of the data it manages, replication isn't even essential. - Valkey: Penpot only needs one Valkey instance to function correctly. Due to the nature of the data it manages, replication isn't even essential.
- User media storage: This should not be configured with local storage but rather with centralized storage, such as Kubernetes PVC or S3. - User media storage: This should not be configured with local storage but rather with centralized storage, such as Kubernetes PVC or S3.
__Since version 2.15.0__
Starting with version 2.15, we have introduced the MCP server. Due to architectural constraints, using the MCP server requires running only a single instance of Penpot.
If the MCP server is not installed, then Penpot can scale normally and multiple application instances may be deployed without restrictions.
## Backend ## Backend
This section enumerates the backend only configuration variables. This section enumerates the backend only configuration variables.