As soon as your Magento 2 site is up and running on MDOQ Hosting there are a few common tasks you may wish to undertake.
By default MDOQ instances aren't configured to send mail. The easiest and most reliable way to send emails is to install and configure an SMTP email module, such as Mageplaza_Smtp.
Because Magento_TwoFactorAuth requires the ability to send emails before you can log in this module is disabled by default. We strongly recommend enabling this module as soon as you have emails set up and configured.
Once enabled we also recommend installing
markshust/magento2-module-disabletwofactorauth as this module will allow you to disable Two Factor Authentication in configuration. This means you can disable for development instances, with no possibility of it being accidentally disabled in source control. (By default you may only disable
Magento_TwoFactorAuth by disabling the module, which makes a change to a file controlled by source control, which can accidentally be committed and taken live).
What does the big red 'Go Live' button do?
By default new production instances will be in development mode.
Development mode is designed to allow you to fully recreate the instance, or specific components when you want. In development mode all components can be fully recreated.
Recreating the MySQL component in development mode will cause any data within the database to be lost
Development mode is ideal for:
- staging a full migration from Magento 1 to Magento 2, as each time you will start with a fresh database.
- Changing the initial installation configuration
You can tell you are in development mode by selecting the production instance.
If you are in development mode you will see two action buttons on the bottom right of your screen: "Go Live" and "Perform Release"
If you are in production mode you will only see one action button "Perform release".
MDOQ production mode and MDOQ development mode are not linked to the current mode the Magento application is running in.
Unless you are doing repeated Magento 1 migrations and you are happy with your installation configuration, we would recommend clicking "Go Live" as soon as possible. This will not perform any action against the production instance, it will just inform MDOQ that it should be treated as a live site.
Recreating the MySQL component in production mode will not cause any data within the database to be lost.
As soon as you have "gone live" we would recommend enabling scheduled backups for the frequency you desire.
This can be done under the "Settings" icon, you can find more information here
A common requirement is SSH access to the production site as well as to any development instances.
Please see the configuring SSH access tutorial.
If you would like additional stores/websites for your production instance. Simply add them in the Magento admin panel. (Making sure they are enabled and have a unique url). Then synchronize the "Environment Changes" component.
Automatic SSL certificate creation and renewal is provided by default for all production sites.
However for MDOQ to be able to generate certificates, the DNS record must point to the site.
Once it does MDOQ will start the process to generate a certificate, this usually takes ~5-10mins but can take longer on busy periods.
(For more information on SSL certificate please see: SSL Troubleshooting: There is an error validating your endpoint)
By default we will set you up with an account within our Github repo. Although you cannot have direct access/control of this repository MDOQ does still allow you to make commits and merges.
You are still able to carry out development work for your production account.
If you would like more control you can of course use your own repository.
If you would like to transfer an MDOQ repo to your account please raise a support request.
Deletion protection stops your instance from being accidentally deleted. It can be enabled under the settings dialog.