6555a68fa9
Serve the front-end sources of the new back-office through the current satellite admin server under the path `/back-office`. The front-end is served in the same way than the current one, which is through an indicated directory path with a configuration parameter or embed in the binary when that configuration parameter is empty. The commit also slightly changes the test that checks serving these static assets for not targeting the empty file in the build folder. build folders must remain because of the embed directive. Change-Id: I3c5af6b75ec944722dbdc4c560d0e7d907a205b8 |
||
|---|---|---|
| .. | ||
| build | ||
| src | ||
| static | ||
| .eslintrc.cjs | ||
| .gitignore | ||
| .prettierrc | ||
| assets_noembed.go | ||
| assets.go | ||
| build-if-changed.sh | ||
| build.sh | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| svelte.config.js | ||
| tsconfig.json | ||
Admin UI
Implementation details
This is a project based on the Sveltekit.
The project is set up with Typescript.
The Web App is currently straightforward as we specified that v1 would be.
The v1 is just a simple web page that exposes the Admin API through some forms and allow to a call the API without needing to use some HTTP REST clients (e.g. Postman, cURL, etc.). It doesn't offer any user authentication; the user has to know the API authorization token for using it.
The UI has a set of Svelte components that collaborate together to render an HTML form with input elements from the Admin API client. The Svelte components expect some values of a certain Typescript interfaces, types, and classes, for being able to dynamically render the HTML form and elements.
Each source has a brief doc comment about its functionality.
Development
Install the dependencies...
npm install
...then run the development server with autoreload on changes
npm run dev
Navigate to localhost:3000. You should see your app running.
Building for production mode
To create an optimized version of the app:
npm run build