I‘m looking for a way to deploy my web app as a Progressive Web App (PWA). PWAs enable coding apps with the standard web programming model, still delivering a device independent installation and runtime behavior on any device.
To enable PWAs I need to basically place two files in the root directory of my web deployment and I need to enhance the header section of the index.html with a statement like
<link rel="manifest" href="manifest.json">
So, very non-invasive, but I didn’t find a way to do this. I’ve experimented a bit with the preview deployment by uploading and changing files via the backend/files console, but didn’t succeed.
Is there a way to enhance deployments in a proper way to achieve this?
We will be happy to assist you. I need to ask you a few more questions so I can help you.
What is your application id, and where is index.html is situated ?
Hi @sergey.kuk ,
Thanks for the offer.
My AppID is 5BDF0E64-9F03-6F8E-FF75-0E183AF61100.
The issue is, I don’t know the conventions behind the file structure and layout which I’m seeing in the file browser (backend/files). There are a lot of index.html in various folders.
For instance, I can start a preview of my page and then modify index.html in folder ‘Root/ui-builder/containers/default’. Using a browser-refresh then shows that my changes are reflected in the preview (I see this using chrome dev tools). So obviously, the preview is served from this folder. However, re-deploying the preview (using the preview button of UI Builder) wipes out my modifications. Obviously there is a generation step which re-generates index.html.
So, I’m looking for a place where I can put in my enhancement (in some template index.html, I guess), so that enhancements survive redeployments/regenerations of preview and of course real deployments.
Similary, I need to place a json-file into the root of the final preview/deployment. But I didn’t find a place where to upload it to, so that it survives the regeneration of the preview/deployment.
Hope this makes sense to you …
@Klaas_Klever unfortunately you should re-add the line each time when you deploy UI
I have created an internal ticket BKNDLSS-24263 to add the possibility to configure header section
As written, the other issue is around providing additional configuration files to the root (or somewhere else) of the deployed web app. Such files support standard web mechanisms like PWA, or other frameworks, like Google Analytics.