Installing the system, its libraries and environment requirements
Steps of installing the extension with the system check, installing the external libraries on hosting, post-installation settings, and the server requirements.
The system installs as an extension package. The installer first measures the server and only allows installation if there is no mandatory (red) error; then it builds the database, the libraries and the default settings step by step, repeatably.
Installation step by step
- In Extensions → Installer upload the installation package (zip).
- In Extensions → Modules install the extension (this only prepares it), then open it for editing.
- Choose the system check and installation tab and review the measurements. Red rows are mandatory errors.
- If there is no red error, click the install button. The steps (check, libraries, database schema, migrations, defaults, registration, finish) run one after another; any of them can be repeated.
- If the libraries cannot be installed from the web interface, extract the library package (libraries.zip) into the storage folder with your hosting file manager, then click the library install button in the system check and check again.
- Set up the scheduler so that background jobs run every minute.
- Complete the settings: data room store and theme (terms pages, mandatory acceptance, brand name), group of new data room users, access check frequency, the client company's contract storage rule in the document centre, mail channel, digital signature settings.
Requirements
| Area | Requirement |
|---|---|
| PHP | at least 8.0 (8.2 or newer recommended), 64-bit recommended |
| Database | MariaDB 10.2.7 or MySQL 5.7.8 and above (MariaDB 10.6 or MySQL 8.0 recommended), utf8mb4 |
| Memory, run time | at least 128 MB (512 MB suggested), at least 120 s run time (300 suggested) |
| Upload | at least 32 MB file size (64 MB suggested) |
| Disk | at least 300 MB free (1 GB recommended); local storage is scarce, Drive is primary |
| Network | outbound HTTPS to the tax authority, Google sign-in, the central bank and the mail provider |
| Scheduler | runs every minute |
Updating
Updates come from a signed package in two stages: preparation (download, signature check, backup) and activation (maintenance, database update, code switch, health check). On failure the system automatically restores the previous code. Database updates of skipped versions run in order.
Example
On shared hosting the web library installation does not run because the server blocks command execution. The administrator extracts the library package into the storage folder with the hosting file manager and clicks the library install button; after re-checking, the library row is green.