During the installation process, the system verifies the actual server configuration and shows the elements that are incorrect and require a change in parameters. Please note that the requirements presented below are not general and not for each installation, for more complex systems they should be verified and optimized individually.
The most recent and complete configuration can be found on GitHub and in the module "Server Configuration" in the developer version:
Core software for the server
- Operating system - Debian, Ubuntu, Mint - works on most Linux distributions. We do not recommend MS Windows operating system as well as MS Windows Server. Although our system works all adequately on Windows servers, it is not an optimal environment in terms of web applications.
- Webserver
- Nginx 1.19 - works also properly on earlier versions, however, the latest stable versions are recommended. You can also use alternative software as long as it is compatible
- Apache 2.4 - works also properly on earlier versions, i.e. 2.1, 2.2, 2.3 (the latest stable versions are recommended). You can also use alternative software as long as it is compatible.
- Database
- MariaDb 10.5 (recommended) - the latest stable versions are recommended. Versions below 10 are not recommended.
- MySQL 5.7, 8.0 -works also properly on earlier versions, i.e. 5.6 (the latest stable versions are recommended). You can also use alternative software as long as it is compatible.
- PHP 7.3 (recommended); 7.2.x, 7.4.x. The latest stable 7 versions are recommended (eg. 7.4.x.
Requirements for data base engine [MySQL]
- SQL_MODE should not contain STRICT_TRANS_TABLE and ONLY_FULL_GROUP_BY
- ENGINE=InnoDB should be available and enabled by default (disable --skip-innodb)
The requirements depend on the system version, recommended configuration:
Requirements for PHP
The requirements depend on the system version, recommended configuration for php.ini:
Third party libraries configuration
- IMAP Mandatory
- PDO Mandatory
- MySQL Native Driver (mysqlnd) Mandatory
- GD Mandatory
- OpenSSL Mandatory
- Curl Mandatory
- PCRE Mandatory
- XML Mandatory
- JSON Mandatory
- SESSION Mandatory
- DOM Mandatory
- ZIP Archive Mandatory
- MBSTRING Mandatory
- SOAP Mandatory
- FILEINFO Mandatory
- ICONV Mandatory
- INTL Mandatory
- SPL Mandatory
- Reflection Mandatory
- SimpleXML Mandatory
- bcmath Mandatory
- filter Mandatory
- LDAP Optional
- EXIF Optional
- APCU Optional
- OPCACHE Optional
- IMAGICK Optional (but recommended)
Correct path configuration to third party libraries
- PEAR
- Net_SMTP
- Net_IDNA2
- Mail_mime
FPM
The requirements depend on the system version, recommended configuration: https://github.com/YetiForceCompany/YetiForceCRM/blob/stable/tests/setup/fpm/www.conf
Web server
Apache: https://github.com/YetiForceCompany/YetiForceCRM/blob/stable/tests/setup/apache/.htaccess
Nginx: https://github.com/YetiForceCompany/YetiForceCRM/blob/stable/tests/setup/nginx/vhost.conf
Privileges to folders and files
Privileges to folders and files are often the most common source of problems for people who install an application on VPS and dedicated servers. There should be the same owner for all CRM files and folders. We prefer such a configuration of files [644] and folders [755] that allow full access from a browser to read and write uploaded files without changing privileges on these folders and files (so the browser has such privileges). It is necessary to remember that when the application is running, it also performs various operations such as read and write as well as creating and deleting files. If you do not know how to configure the privileges, ask your administrator to do it and send him a link to this article.
- Configuration directory config
- Application data directory app_data
- User privileges directory user_privileges
- Tabdata File user_privileges/tabdata.php
- Menu file user_privileges/menu_0.php
- User privileges file user_privileges/user_privileges_1.php
- Cache Directory cache/
- Address book directory cache/addressBook/
- Image Cache Directory cache/images/
- Import Cache Directory cache/import/
- Logs directory cache/logs/
- Session directory cache/session/
- Cache templates directory cache/templates_c/
- Cache upload directory cache/upload/
- Vtlib test directory cache/vtlib/
- Vtlib Test HTML Directory cache/vtlib/HTML
- Cron modules directory cron/modules/
- Modules Directory modules/
- Storage Directory storage/
- Product Image Directory storage/products/
- User Image Directory storage/users/
- Contact Image Directory storage/contacts/
- MailView attachments directory storage/OSSMailView/
- Logo Directory public_html/layouts/resources/Logo/
- E-mail client public_html/modules/OSSMail/
- Third party libraries public_html/libraries/
Supported browsers
A user should always have the most up-to-date version of a browser because only the most recent versions support the newest web technologies. Below is a list of browsers from the one that is the most recommended for YetiForce (Google Chrome) to the least recommended.
- Google Chrome
- Firefox
- Opera
- Internet Explorer
- Safari
- Other
Additional configuration using .htaccess
Some servers allow changing the configuration via the .htaccess file. We present some of the examples below.
Apache module (as set in httpd.conf "AllowOverride Options" or "AllowOverride All")
<IfModule mod_php5.c>
php_flag log_errors On
php_flag display_errors Off
php_value error_log cache/logs/phpError.log
php_value memory_limit 512M
php_flag output_buffering On
php_flag zlib.output_compression Off
php_flag file_uploads On
php_value upload_max_filesize 100M
php_value post_max_size 50M
</IfModule>
FastCGI module
<IfModule fcgid_module.c>
FcgidIOTimeout 600
FcgidConnectTimeout 600
FcgidBusyTimeout 600
FcgidIdleTimeout 600
</IfModule>
<IfModule mod_fcgid.c>
IdleTimeout 600
ProcessLifeTime 600
IPCConnectTimeout 600
IPCCommTimeout 600
BusyTimeout 600
</IfModule>
Additional configuration using user.ini
You can also quickly change the PHP configuration by creating a user.ini file in the main directory ($_SERVER['DOCUMENT_ROOT']), right now it supports CGI/FastCGI. However, be careful because not all parameters can be configured in this way (https://www.php.net/manual/en/configuration.changes.modes.php).
More information available: here.
Example: https://github.com/YetiForceCompany/YetiForceCRM/blob/stable/.user.ini
HTTPS and HTTP2 encryption
We strongly recommend to always encrypt the connection to the server where YetiForce is installed. If the connection is not established through the HTTPS protocol the communication may be intercepted or altered by third parties.
REQUIREMENTS FOR THE SYSTEM UPDATE
MySql
connect_timeout = 3600
connect_timeout = 3600
net_read_timeout = 3600
net_write_timeout = 3600
wait_timeout = 3600
wait_timeout = 3600
innodb_lock_wait_timeout = 3600
PHP
max_execution_time = 3600
max_input_time = 3600
default_socket_timeout = 3600
FPM
pm.process_idle_timeout = 3600s
request_terminate_timeout = 3600
Nginx
server {
...
client_body_timeout 3600;
send_timeout 3600;
location ~ \.php$ {
...
fastcgi_send_timeout 3600;
fastcgi_read_timeout 3600;
keepalive_timeout 3600;
proxy_connect_timeout 3600;
proxy_send_timeout 3600;
proxy_read_timeout 3600;
}
location ~ ^(.+\.php)(.*)$ {
...
fastcgi_send_timeout 3600;
fastcgi_read_timeout 3600;
keepalive_timeout 3600;
proxy_connect_timeout 3600;
proxy_send_timeout 3600;
proxy_read_timeout 3600;
}
}