Below you will see the list of the configuration files available for editing in the database servers:
To get more information on which settings can be changed in the provided config folders, use the appropriate descriptions:
MySQL and MariaDB also include my.cnf config file for database settings. Note that if you change any configurations in this file you need to delete the following string in order not to lose your custom settings while update:
#Jelastic autoconfiguration mark.
The database servers include a cron folder with the config file, where cron jobs can be configured.
For example, here you can set the scheduled backups of your database. For MySQL, MariaDB and MongoDB servers, there are already cron settings which can be used to run the default backup script. These settings just need to be uncommented and edited based on the custom requirements.
The detailed information on Cronjob configuration can be found in the Setting Up a Cronjob document.
This folder is used for storing the backup files of your database. These files can be used for restoring the data.
The instructions on how to restore these files can be found in the following documentation:
The keys directory is used as a location for uploading any private key which is needed for your application.
Generate the key, save it as a simple file and upload to the key folder. Now you can use it for different cases by simply stating the path to your key:
The conf.d folder is usually used for storing and managing sub configs.
In conf.d folder you have access to the MyAdmin-jel.conf (for MariaDB and MySQL), phpPgAdmin (for PostgreSQL) and couchdb.conf (for CouchDB) files.
These files can be edited in order to set appropriate criteria for allowing or denying access by IP address or domain to the application with the database on an Apache web server level.
The main configuration files of the PostgreSQL database server are located in the conf folder.
This folder is used for storing and managing the main CouchDB config files.