Deployment

Code Bundling

Development vs Production mode

When deploying your application, make sure that you bundled ActiveUI in production mode. This will ensure that the code is minified and will disable all costly developement assertions and warnings.

Application Server

Where to deploy?

There is no server component to ActiveUI: once compiled, it is reduced to a set of static HTML, CSS and JavaScript files. This means that any HTTP server able to serve static files can serve your ActiveUI application.

As to where to deploy ActiveUI, here are the different possibilities architecture-wise:

  • With serve to try your production build locally.
  • In the same application server that serves ActivePivot: we usually recommend such setup for quick deployment, debugging purpose or when there is only one existing ActivePivot application.
  • In a separate server, distinct from the ones hosting ActivePivot: this option is best suited for complex architecture where there are multiple ActivePivot servers involved (distributed or not), so that restarting a server would not interrupt the communication with other backends. If all those servers share the same Content Server, it can be relevant to serve ActiveUI from that Content Server.

Gzipping

Whichever application server is used (Jetty, Tomcat, etc...), please make sure that compression is enabled for both:

  • The server hosting ActiveUI
  • The server hosting ActivePivot Server

This will ensure that static files such as ActiveUI HTML, CSS and JavaScript resources, but also results from REST calls and data sent through WebSockets from ActivePivot server are compressed.

← DebuggingInternationalization →