Skip to content
GitLab
    • Why GitLab
    • Pricing
    • Contact Sales
    • Explore
  • Why GitLab
  • Pricing
  • Contact Sales
  • Explore
  • Sign in
  • Get free trial
  • Fediventure
  • Fediventure
  • Issues
  • #2

Basic Federation

This is meant as a temporary solution until something more sophisticated is agreed upon.

  • Connect to backend server based upon apiUrl property of the map, with the fallback being derived from the map url (the apiUrl will by default be the URL of the map with everything after the host (or port) stripped). if there is no apiUrl property, it should not federate.
  • Disable any kind of authentication (JWT and CORS) in pusher.
  • Choose Jitsi Instance based on jitsiUrl property of the map, default to meet.jit.si. This is now deprecated it favor of the jitsiUrl property per jitsi layer, as implemented upstream. The behavior of jitsi layers without jitsiUrl property is undefined.

It is that simple.

We are currently working on adding federation to workadventure-xce

Edited Mar 23, 2021 by Jstsmthrgk
Assignee
Assign to
Time tracking