Hi, On Thu, May 27, 2021 at 3:56 PM Bruno Borges <bruno.bor...@gmail.com> wrote:
> I've been reading the GWT documentation and trying to understand the > deployment model of the front-end, especially for PWA apps (but not > exlucisvely!) to find a scenario where GWT front-end could be deployed to > Azure Static Web App service (to serve the static content), and then the > back-end APIs deployed as an Azure Function. > > I wonder if anyone has played with the general idea of deploying > front-end on a different server (Nginx/Apache) only to serve the static > content, and the actual API back-end to another. > This is the way we deploy most of our applications and it is not really any different from how you have to do it for any other javascript context and the standard security concerns. The only tricky part really is working with your transport layer. If you are using GWT-RPC (which I recommend against) then you are stuck updating the server and the client at the same time if you ever change the API in a backward incompatible manner and you have to do some ugly configuration of base url of services. Assuming the Azure Function can be accessed as http calls then you should be fine. If you are using the "builtin" support for separating our resources (i.e. GWT.getHostPageBaseURL(), GWT.getModuleBaseForStaticFiles(), GWT.getModuleBaseURL()) for accessing assets then you may find some things break for local development when GWT.getModuleBaseForStaticFiles() != GWT.getModuleBaseURL() as GWT.getModuleBaseForStaticFiles() does not take into account the debug hooks but this is pretty rare scenario. Is there a specific problem that you are having? -- Cheers, Peter Donald -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc5K_0QrVz-RoMiEH7FYYBjdx7XAsBsz_u1%3DH2So3etOyA%40mail.gmail.com.
