This paragraph provides some guidance in server hard- and software requirements.
The server does not need to be a high performance computing server, the back-end server(s) do the hard computational work.
Depending on the type of deployed applications, the dataflow can be significant and needs to be managed in-memory.
The duration of computations and the number of simultaneous users need to be accomodated. If there are many users doing many long-running computations, the server resources (memory) and number of simultaneous PHP processes need to be scaled up accordingly.
Server Hardware Requirements
The server is provided as a Docker image. Hence any server that is able to deploy docker images can be used.
CPU and Memory
As for any web application, you should size your server based on the traffic on the site.
Typically analytics applications deployed through the Portal Server are quite data intensive. During interaction with the server all data, including file up- and downloads, lives in memory in the Portal Server.
It is recommended to assign 512MB per simultaneous active server request. If applications do not do significant file up- and download this can be reduced.
The Portal Server Docker image is less than 150 MB.
The main driving factors behind required additional disk space are:
- Temporary storage of up- and downloads.
- The amount of front-end versions to be supported (current production versions < 10 MB each).
- Logging enabled in combination with traffic through the server.
Logging directory can be configured outside the installation directory (recommended).
Particularly when traffic logging (intended for debugging purposes only) is enabled for an application log files can grow rapidly.
Apart from disk space for file storage and logging it is recommended to allocate at least 1GB of diskspace for the application itself.
The Portal Server should run on all recent browsers in the market, including but not limited to:
Development and testing is primarily being done with Chrome and Firefox.