...
There are two options how to deploy GRAVITY on-premises, either on a Java Runtime or as a Docker container (same memory specs)..
Java Runtime
GRAVITY needs a database and a java runtime Java Runtime to work.
Application Server |
---|
Database |
---|
minimum 1024MB RAM platform independent |
min. 768MB RAM
with Java 17 runtime installed open port 443 and 80 |
JRE 1.8+
reachable from clients which will use GRAVITY |
db user
db password
db uri or host and port
MariaDB, MySQL 8 or Oracle DB (12.2+)
empty db
If you host a custom config server too, it needs to be within reach of clients and server of course.
...
title | Docker |
---|
...
has fontconfig and any font installed (apk --update add fontconfig ttf-dejavu) | Supported RDBMS: Oracle Database, MySQL, MariaDB. The following versions of them are supported by SLA, but other version might work as well:
|
Docker
Check the Docker wiki page (gravity.docker.run) for guidance on Docker setup and requirements.
Configuration requirements
...
For better understanding, we are using a fictional company called gravifygravify.io.
Item to note | Example for gravify.io |
---|---|
A list of URLs on which GRAVITY shall be enabled | portal.gravify.io gravify.io/sites gravify-io.sharepoint.com/layouts Exclude: gravify.io/sites/management |
An URL where the users will need to go to start GRAVITY (first time) | portal.gravify.io/home |
An SMTP user and password, it will be used to send notification mails from the backend server | devops@gravify.io |
An e-mail address user can turn to when they have issues | int-help@gravify.io |