Create a gui to interact with the system¶

After built, there will be a package bundle.

What is needed to serve the frontend is actually:

• a appserv that provides text/html for entrypoint GET /index
• a appserv that provides application/javascript for entrypoints GET /index.bundle.js
• a appserv that provides application/javascript for entrypoints GET /index.bundle.js.map

All these things can be provided by the REST service itself by a a static route.

That said. The REST Service providing API should keep this staff well separeted.

Or, by option. It is possible to serve this to a separate subdomain/ subpath. This second option can require another gateway or ingress definition that I am not akin to define because I am really lazy and running in idiot-mode.

So, single service¶

• /apis/{:whateverhere}
• /index
• /index.bundle.js
• /index.bundle.js.map
• /favicon.ico

HOW:

static pages: loaded from folder assets/ in the project in RUST.

During deployment: folder assets/ is a PersistentVolume mounted in the right place.

REST API service has an environment variable for assets/ folder

ASSETS_FOLDER=/assets

Thats it