You can customize PHP service settings for PHP-FPM and CLI containers by adding a php.ini file to the root directory of your Adobe Commerce project. The FPM container includes the following volumes: The following example adds the analysis-stempel and analysis-nori plugins to the Docker environment.ĭocker base image: magento/magento-cloud-docker-php, which is based on the php Docker image When you generate the docker-compose.yaml file, you can add additional custom plugins to the Docker environment using the ES_PLUGINS environment configuration option. If you use Elasticsearch 6.5 and later, the default Elasticsearch plugins are installed automatically along with any custom plugins added to the services.yamlfile.
The analysis-icu and analysis-phonetic plugins are installed by default and can not be skipped. If your Cloud project uses Adobe Commerce version 2.3.5 or earlier with MySQL search, add the -no-es option to skip the Elasticsearch container configuration when you generate the Docker Compose configuration file: ece-docker build:compose -no-es. See Important Elasticsearch configuration in the Elasticsearch documentation for details about available configuration options. Php vendor/bin/ece-docker build:compose -es-env-var = ES_JAVA_OPTS = "-Xms512m -Xmx512m" -es-env-var =_mmapfs = false Use a mount to add a custom my.cnf file to the services section in the file: You can inject a MySQL configuration into the database container at creation by adding the configuration to the docker-compose-override.yml file using any of the following methods: You must manually destroy the database volume using the docker volume rm command. The next time you use the docker-compose up command, the Docker environment restores your database from the persistent volume. To prevent accidental data loss, the database is stored in a persistent magento-db volume after you stop and remove the Docker configuration. Files are executed in alphabetical order. sql.gz extensions that are found in the /docker-entrypoint-initdb.d directory. The initial start-up process also executes files with. When a database container initializes, it creates a new database with the specified name and uses the configuration variables specified in the docker-compose configuration. To use MySQL for the database, add the -db image option when you generate the Docker Compose configuration file. docker/mysql/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d The default configuration uses the mariadb image and includes the following volumes: You can configure the database container to use either MariaDB or MySQL for the database. See Service configuration options to customize container configuration when you build the Docker compose configuration file. The following containers provide the services required to build, deploy and run Adobe Commerce sites.
#Setting up rational application developer for tls 1.2 code
Deploy code and migrate static files and data.Prepare to deploy to Staging and Production.Example of managing system-specific settings.Configuration management for store settings.Set up multiple Cloud websites or stores.Additional tools for file synchronization.
0 kommentar(er)
