What are the HW/SW requirements for running Tritius on your own server?

Please see our documentation Technical requirements for running the Tritius system on your own server.

How do I prepare a server for running the Tritius VM?

First it is necessary to prepare a virtualisation environment and run Tritius in it. We offer two options:

1. The customer gives us remote access to their server. We install and configure the virtualisation solution (VirtualBox) ourselves and start the virtual machine ourselves.
2. We hand the virtual machine over to the customer, who starts it within their own virtualisation solution and ensures its operation as a service.

Next, the network needs to be configured so that we can reach the virtual machine remotely, see Network infrastructure.

Is it necessary to back up the whole VM?

No. We strongly recommend backing up primarily the user data itself (the database and the /tritius folder).

Backing up the VM is only an auxiliary mechanism for faster recovery in the event of a failure - a VM backup additionally contains the exact configuration of the whole system in the customer's specific environment.

In practice we recommend backing up the VM only after a configuration change (e.g. enlarging the disk). But even this is not necessary; it is always possible to restore from our VM template + import your user data, it just takes a little longer.

How is the security of the VM ensured?

We supply Tritius in the form of a virtual machine and bear full responsibility for it, just as we previously bore responsibility for the installed application.

We use current versions of operating systems and software tools that are generally considered very secure (Linux Debian, Apache Web Server).

We observe security rules and standards and monitor the system remotely.

For customers with above-standard security requirements we recommend Secure placement in the network infrastructure.

What should I do if the virtual machine is damaged?

If the virtual machine fails (damage to the virtual disk, OS, etc.) and remote access to it is no longer possible, the following solutions exist.

1. Restoring the VM + importing a data backup if necessary.
   1. Restoring from a VM backup. A VM backup may contain current data, but it may not. VM and data backups often run separately, so in the standard scenario we count on restoring the VM + importing data from a backup.
   2. Restoring from the VM template. Backing up the VM is only an auxiliary mechanism for faster recovery in the event of a failure - a VM backup also contains the exact configuration of the whole system in the customer's specific environment. It is always possible to use our template directly instead of a VM backup, perform a quick configuration and then import the data from a backup.
2. Remote access to the virtualisation tool (console), which is possible by mutual agreement (we will help you with common problems) and makes it possible to resolve simpler faults (such as a duplicate IP address in the network, etc.) faster.

Do I need my own SSL certificate to run Tritius (under HTTPS)?

Yes, you need your own certificate, but you do not have to buy it. We will issue it for you free of charge with the help of the Let's Encrypt service. The certificate is then valid for 90 days, but the VM we supply also includes its automatic renewal.

So you do not have to worry about anything or pay anything, and the system will run securely under the HTTPS protocol.

Detailed documentation on using the Let's Encrypt certification authority: Let's Encrypt certificates