Configuration of system constants and directories
The system settings of the platform are regulated in configuration files. Such JSON files contain various parameters of the platform components, such as templates, dictionaries and lists of constants. If necessary, these files can be modified by users to customize the system to suit their needs.
If you are not sure that you will be able to create and customize a custom configuration yourself, we strongly recommend that you do not make changes to the config files. If you do decide to change the system configuration, do not edit the original configuration files. In case they are damaged or lost, the platform operation will be disrupted.
Creating a custom configuration
In order to change the JSON configuration, you need to create a copy of the original file and rename it to "custom.<original_name>". Next, you can make the necessary changes to the copy of the file and save it. The next time you run the platform, the system uses the new custom config file.
For example, you want to add new cities to the "cities.json" config. To do this, create a copy of the "cities.json" file, rename it to "custom.cities.json" and move it back to the "json_consts" folder. Any changes to the platform are made only after it has been rebooted, so you will need to restart the platform after saving the new config.
Settings from custom files like custom. will be loaded in priority. If critical errors are detected in this config file, the system will notify the user that the configuration is not working correctly. In such a case it is necessary to delete the created custom-file from the folder, then at the next startup the platform will load the default configuration.
To configure custom communication channels from the "channels " folder, it is not necessary to add the custom. string to the name of the custom config. Files with the "mta_" prefix can be reconfigured via Admin Panel.
List of JSON configurations
| File | Description |
|---|---|
| bots_ip.json | Contains a list of IP addresses to be identified as bots, and the actions associated with those addresses |
| bots_ua.json | Contains a list of UserAgents that will be identified as bots and the actions associated with these agents |
| browsers.json | Dictionary of major browsers |
| cities.json | cities.json |
| countries.json | Dictionary of countries |
| default_eventgen.json | Event Generator default settings |
| devices.json | Dictionary of device types |
| domain_groups.json | Dictionary of domain groups for MTA ISPs |
| genders.json | Dictionary of sex and genders |
| languages.json | Available languages for the platform interface |
| oses.json | Dictionary of Operating Systems |
| platforms.json | Dictionary of major user platforms |
| preset_reports.json | Standard metrics for the summary report |
| sender_types.json | Sender types supported by the platform |
| sql_requests.json | SQL query templates |
| tlds.json | Dictionary of top-level domains |
| tzones.json | Platform-supported time zones |
| reports/channels.json | Channel report parameters |
| reports/traffic.json | Traffic report parameters |
| tag_manager/built_in_vars.json | Tag manager system variables |
| platforms.yaml | Additional config file to define the user's platform and OS |
Configurations reconfigurable in Admin Panel
| File | Description |
|---|---|
| mta_globals.json | General MTA-sender settings |
| mta_isps.json | MTA-sender ISP strategies |
| mta_lock_rules.json | MTA-sender locking strategies |
| mta_retry_rules.json | Strategies for retries on the MTA sender |
| mta_strategies.json | Strategies for sending on the MTA sender |