XYZ federation with codespaces

[dbauszus-glx]

It is possible to create a private fork of the XYZ repository and add resources to this private fork.

XYZ resources are code as configuration, eg. workspaces, templates, and plugins.

The XYZ fork can be launched in Github codespaces.

XYZ forks can be linked to Vercel to allow for preview and production deployments after changes to the resources in the fork are commited.

The fork can be rebased from the XYZ repository itself.

XYZ instances have access to local resources or resources from a CDN, eg. cloudfront.

XYZ instances should be able to request resources from other XYZ instances.

This would allow one fork to use templates from another fork. Both can either run in codespaces or be deployed.

A possible federation of instances could take the shape of multiple client forks with a workspace and resources specific to the client, eg application view templates. Another private fork of the XYZ repository could hold shared templates [layer, views] and plugins.

A client fork instances could access the shared templates. This would allow to do the development and testing in codespaces. An additional benefit would be a catalogue service since the templates repository is a fork of the XYZ repo itself and can serve and test any template through the XYZ process itself.

A client fork with access to a private fork with plugins could sign requests for these plugins to be loaded into mapp from the linked [plugins] instance.

Access from one instance to another could be secured with private keys.

[RobAndrewHurst]

This can also facilitate different utility services such as auth, mail, aws, google, here, mapbox.
Allowing us to split out and fix crucial maintenance tasks easier.

eg. if we need to update a dependency because of a security issue, we won't need to deploy 40+ instances, but just one that is providing the utility service.

[RobAndrewHurst]

We could also look at this from a proper mono-repo perspective where EVERYTHING can exist in one repository which is made from 'sub-modules'.

Monorepos - How the Pros Scale Huge Software Projects // Turborepo vs Nx