SoftService Requirements for web server configuration DMCompile

Requirements for web server configuration

Information for DMCompile incoming operator software users

We recommend using:

- modern (released no earlier than 2016) linux as an operating system,
- nginx as a web server,
- php-fpm as a php process manager.
You can also run the system under Windows, in which case the simplest option would be to use apache2… + mod_php with a set of required extensions. In the description of the directory, you need to register the CUSTOM client provided to you (clientcustomname): SetEnv CUSTOM clientcustomname

Example of a block:

<Directory "C:\www\html">
Options -Indexes +FollowSymLinks
AllowOverride All
Require all granted
SetEnv CUSTOM clientcustomname 
</Directory>

Сonfigure DirectoryIndex in the web server setup:

For Nginx:

index default.php index.php index.html index.htm;

For Apache:

DirectoryIndex index.php default.php index.html index.htm

If the web server will be located on a local network, you will also need external static IP address to it.

Each project has its own implementation features, which are reflected in their configurations. Each project has the API project attached to it, its directory must be called api-incoming and must be located on the same level as the main project (B2B / B2C and others) in file system

Before installing the configs on your server, you need to: Replace the example paths in the configurations with the actual ones for your server. For example such as:

Before install configuration you have to check and correct:

In default file, uncomment the include directives for folders with the components that you have installed
Replace root path directive with actual one
Replace php-fpm socket path for actual one(see fastcgi_pass directives )
Replace the $CUSTOM variable in the sites-available/default file (replace clientpseudonym with your alias). You can also directly register it in the folder configs ( fastcgi_param CUSTOM $CUSTOM; ) by replacing the variable - with the value
Change in sites-available/default the domain name example.com to yours in all places
If you will use https protocol, make a server block for it, similar to what is already there.

You can find the CUSTOM value in the installation task.

Users and access rights
Because your server configuration depends on your linux distribution users can have different names - hereinafter the following user names will be used:
- User www-data - the user under which php-fpm is running from
- Group www-data - primary group of user www-data
- User developer - user for SOFTservice team. We use it for install and upgrade our code
Provide SSH access (recommended) or FTP access (not recommended) for user developer.
Required rights for users developer and www-data
- User - www-data
- Primary group - www-data
- Right for new files - 664
- Right for new directories - 775
- Owner group for new files/directories - www-data
- Owner for new files/directories - www-data
- User - developer
- Primary group - www-data
- Right for new files - 664
- Right for new directories - 775
- Owner group for new files/directories - www-data
- Owner for new files/directories - developer
User developer can be added to secondary groups if you need it
After final configuration users developer and www-data should have same rights to set permissions and edit files / folder

Make sure that the appropriate permissions and owners are set on all files/folders of all sites that the developer and www-data users will have access to

To set public permissions on created folders and files, you need to set a new value for umask in /etc/profile file. To do this, open this file and change/add the following line at the beginning of the file umask 002

You can change the mask for a particular user's terminal shell by adding a line with the umask command to the ~/.bashsrc file . This is actual for Debian-based distributions. Other distributions may require editing the .profile file - check the instructions for your distribution (or your shell)

To check the settings, log out and log in, create a file and folder, make sure that the rights to the created objects meet the requirements

After deciding whether the sites will be located on the same domain or be located on subdomains of the same site, or each will have its own domain, leave the comment in the task ticket at which URLs they should be available. Also, write down logins and passwords to enter, to check the performance of the installed system.e modules

If you need training or help building the product, please contact us.