Migration: v2 -> v3 keep Room URLs

[Jan]

Hi folks,

I migrated from v2 to v3 following the migration guide as described at:
https://docs.bigbluebutton.org/greenlight/v3/migration/

All rooms where migrated correctly - however, the URL changed.
For instance - in v2 people were invited to access /b/jan-wew-ke6 (due to having /b as a prefix), whereas in v3 people receive http-404 when accessing this link. One has to use /rooms/jan-wew-ke6/join instead.

This is a bit problematic IMHO, because these URLs a public, bookmarked and used in calendars, on websites, etc. Has anyone run into this issue so far? I wasn't able to find anything related to it at https://docs.bigbluebutton.org/greenlight/v3/migration/#rooms-migration - sorry, if I missed something.

I'm tempted to rewrite / forward the old-schemes using nginx, however, I'm hesitating: actually, I'm a bit surprised that this functionality is not yet present in greenlight - dedicated entries appear to be missing in routes.rb. I wonder:
- Is there any problem with forwarding /b/jan-wew-ke6 to /rooms/jan-wew-ke6/join in nginx? 
- Are there other deeplinks (i.e. sub-urls) that one need to map accordingly?
- Is there a specific reason why rooms-urls were changed from v2 -> v3 without backwards compatibility?
- What would be a proper pattern / rewrite scheme? Has anybody done this before?

Thanks,
Jan

[Jean Pluzo]

Hi,

I have modified the nginx config file to forward a room to another. For me it was jus a simple return 301 (http moved permanentyl) in the nginx config file. Have not had any complaints.

Can't say if there are other "deeplinks".

Regards,

J.