For high access numbers, it is advisable to run VIMP on several servers in order to distribute the load.
All you need to do is install VIMP on the desired number of servers. The special feature here is that all VIMP installations must access the same database. This can either be on a separate server or on one of the web servers. It is important that it can be accessed by all VIMP instances.
Visitors to the website can now access one of the installed servers via an upstream load balancer (this must support sticky sessions and must not be configured in round robin mode).
In the standard case, each VIMP instance receives its own storage, which is located in the userdata directory. As a result, an uploaded video is initially only stored on the corresponding web server via which it was uploaded.
However, the medium should of course be available on all web servers. There are basically two options for distributing the files across all servers:
Server synchronization:
By activating and configuring the “Transfer” module, uploaded media are synchronized to all other servers in the cluster network.
Activate the transfer module here under Configuration -> Clustering -> Transfer.
Then enter all servers in the cluster under “Transfer” in the top navigation of the Admin Panel. For each server, create a new entry with any name and the complete URL to the server (e.g. https://server1.meinvimp.com). It is therefore important that each server is directly accessible under its own domain.
Finally, open the options menu of the entry that describes the current server and click on “Set”. This defines this entry as the master entry for the current server. Proceed in the same way with all other servers in the network until each server has its “master” entry.
Finally, you only need to set up a cron job to ensure that the synchronization task runs:
1 * * * * * php -f /path/to/vimp/vimp -- framework:transfer > /dev/null 2>&1
In the above example, replace /path/to/vimp/ with the actual path to your VIMP installation. If you are using a version of VIMP lower than 6.0, also replace “vimp -- framework” with “symfony -- framework”.
Media located in the portal are then regularly synchronized between all servers.
Central storage:
As an alternative to synchronizing the media, you can also integrate a central storage (e.g. a NAS). To do this, the NAS must simply be mounted on the userdata directory in each of the VIMP installations. This means that all media is stored centrally and synchronization is not necessary.