From e8a361f11cc22a004baa74727ba4497f985fe135 Mon Sep 17 00:00:00 2001 From: Daniel Molkentin Date: Wed, 19 Jun 2024 19:05:26 +0200 Subject: [PATCH] fix: correct statements about presentations not being migrated and how to fix entity too large errors --- docs/docs/greenlight/v3/migration.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/docs/greenlight/v3/migration.md b/docs/docs/greenlight/v3/migration.md index 18131aef89..b7e0dc8156 100644 --- a/docs/docs/greenlight/v3/migration.md +++ b/docs/docs/greenlight/v3/migration.md @@ -147,7 +147,9 @@ Important notes: - Only the Rooms of the active users will be migrated - The migrated rooms will be assigned to their respective migrated users on v3 -- The presentations will not be migrated - the presentations will need to be re-uploaded to v3 by the room owner or shared access user. +- With the most recent patch releases of Greenlight 2, the presentations will be migrated if present on the source system. However: + 1. If presentations are referenced in the database but *do not* exist on disc they will be ignored. + 2. If this step fails with a `413 Entity too large` error, you need to increase the `client_max_body_size` setting in the nginx reverse proxy of your *Greenlight 3* instance and retry. If you use another reverse proxy, consult your manual about increasing the maximum body size for HTTP requests. **To migrate the rooms, run the following command:**