xyz-host deployments with custom views and external mapp library.

[dbauszus-glx]

xyz [/mapp] was built with the idea to quickly develop, test, and deploy a serverless spatial data interface. The mapp library provides a browser API and ui elements to build app views to connect to the data through the xyz-host.

For development and testing it makes sense to have xyz and mapp in the same repository. Some features do require changes to the xyz and mapp code. However most features are implemented in the mapp library or through plugins first.

Application views, such as the _default.html mapp view are language templates that can be referenced in the workspace to be loaded from a src [https, file, cloudfront]. The template itself will be cached for the lifetime of the workspace which can be controlled.

eg.

  "templates": {
    "_default_view": {
      "en": "https://geolytix.github.io/mapp/views/mapp.html"
    }
  },

The src of the mapp module can be defined in custom app views.

eg.

    <!-- Load XYZ / MAPP stylesheet and library. -->
    <link rel="stylesheet" href="https://geolytix.github.io/mapp/lib/mapp.css">
    <link rel="stylesheet" href="https://geolytix.github.io/mapp/lib/ui.css">

    <script type="module" src="https://geolytix.github.io/mapp/lib/mapp.js" defer></script>
    <script type="module" src="https://geolytix.github.io/mapp/lib/ui.js" defer></script>

We should have a xyz-host branch [or fork] where we remove elements not required for a deployment.

The mapp library should never be required to be built in a deployment and the development dependencies should be removed from this branch.

Testing resources should also be removed in the xyz-host branch. There should be a script that syncs the branch for commits behind while ignoring the commits ahead in which elements not required are removed.

A deployment can be linked to a mirrored fork allowing for redployment when templates in the forked repo are updated.

The latest version of the mapp module with a cdn src can be loaded in the client as soon as the hosted version is updated. No re-deployment will be required.