Sign in into https://magento.cloud, go to Account settings tab and add your public SSH key.
If you do not have SSH keys, you can generate a new key pair using the following command:
ssh-keygen
The new public key will be saved in the ~/.ssh/id_rsa/pub file.
Go to the Projects tab and select a project. Clone the project using a git link in a web UI:
git clone <projectid>@git.eu-3.magento.cloud:<projectid>.git magentolive
cd magentolive
Rest of commands will be performed from the project directory.
A Magento Cloud instance as well as a deployment process can easily be customized through configuration files and environment variables. The environment variables can be added through web UI or cli utility.
The ADMIN_PASSWORD variable controls a password of the admin user. To change the admin's password, go to the Configure environment > Variables and add the following environment variable:
ADMIN_PASSWORD = magentolive18
When you save changes, a deployment process will be started in order to apply the changes. When it is done, you can sign in to admin backend using password you have set. You can access the admin backend using a link from web UI + /admin
It is easy to clone branches using web UI. The codebase as well as database are copied to a new virtual machine, then a deployment process is started in order to change BASE_URL.
To clone a branch click on the branch button in the top right and set a name of the new branch:
The current branch will be cloned and new deployment started. It will take up to few minutes to finish the clone process.
To install a custom theme just put it into app/design directory, commit and push changes.
The Dark theme is the copy of Magento/Luma theme with dark gray background.
mkdir -p app/design/frontend/Vendor/
curl -L https://github.com/yyevgenii/mageconf17/raw/master/resources/dark.zip -o dark.zip
unzip dark.zip -d app/design/frontend/Vendor/
rm dark.zip
git add app/design/frontend/Vendor/
git commit -m "Add Dark theme"
git push
If you do not have installed curl utility, you can try to download file with wget:
wget https://github.com/yyevgenii/mageconf17/raw/master/resources/dark.zip
or download the file using a web browser.
After deployment you have to switch to the Dark theme:
- Log in to admin backend
- Go to Content > Configuration page
- Open global scope to edit
- Switch Applied Theme to Magento Dark
- Save configuration
Go to storefront to check changes.
Add the following lines at the end of .magento/services.yaml:
elasticsearch:
type: elasticsearch:2.4
disk: 1024
Add the elasticseach line into relationships section in the .magento.app.yaml:
elasticsearch: "elasticsearch:elasticsearch"
The result relationships section should look like this:
relationships:
database: "mysql:mysql"
redis: "redis:redis"
elasticsearch: "elasticsearch:elasticsearch"
Commit and push changes:
git commit -am "Enable Elasticsearch service"
git push
During the deployment process the Elasticsearch service will be installed and configured as well as the Magento catalog search engine will be switched to the Elasticsearch. Go to admin backend to verify changes, the search engine settings are located at Stores > Configuration > Catalog > Catalog > Catalog Search:
This trick decreases maintenance time by moving the setup:static-content:deploy step to the stage build. On the build stage a database connection is not available and we do not know for which locales we have to generate static assets. But we can store locale settings in a file and pass locales to the setup:static-content:deploy command.
For dumping the locale settings login into SSH console and run the following command:
php vendor/bin/m2-ece-scd-dump
The locale settings will be dumped into a app/etc/config.php file. Download this file using scp utility, commit it and push changes to git:
scp [email protected]:app/etc/config.php app/etc/config.php
git commit -m "Add locale settings into config.php" app/etc/config.php
git push
During the deployment process you will see that the static assets generation runs before maintenance mode is being enabled. In this way we have decreased a downtime caused by a deployment process.