Magento 2's command line tool has some handy commands. These commands can be added to cron system to take automated backups. Rollback is another interesting command, it will place the site in the maintenance mode, restores the DB, files and media, and then enables the site.
setup:backup Takes backup of Magento Application code base, media and database
setup:rollback Rolls back Magento Application codebase, media and database
info:backups:list Prints list of available backup files
In addition to the above Schogini.biz has a handy module that can further augment the backup/rollback system.
schogini:cloudbackup Backup code, media and DB to Amazon S3 Cloud
schogini:cloudrollback Rollbacks code, media and DB from Amazon S3 Cloud
Introduction of the PHP based dependency management using "composer" makes life easy. Composer to ensures the all components maintain their expected versions. With a single command, "composer update" all core and third party modules get updated.
The flag is relocated inside the var folder, in addition it, we can add the IPs to be allowed in a file var/.maintenance.ip
Manual creation of the flag file and the IP file not needed, instead we can use the bin/magento command line tool.
maintenance:allow-ips Sets maintenance mode exempt IPs
maintenance:disable Disables maintenance mode
maintenance:enable Enables maintenance mode
maintenance:status Displays maintenance mode status
This module is useful during the development phase where static file creation is done to save speed of iteration, uncaught exceptions are shown on the browser, error handler exceptions are not logged and very detailed error reporting in var/report.
Live shop should be in this mode where, maximum performance abd security are assured. In this mode exceptions are not shown to the user but only saved to the logs. Static files are not created for any changes made thus the docroot folder can be in read-only mode!
This mode is not needed! Neither good for production nor development.
Installing of new modules is much easier in Magento 2. Add the modules version and repository details to the composer.json and running the install command will save the module. Once this is done we can run the bin/magento CLI tool to install the module.
module:disable Disables specified modules
module:enable Enables specified modules
module:status Displays status of modules
module:uninstall Uninstalls modules installed by composer
PSR which stands for PHP Standard Recommendation. In this currently there are three standards. PSR-0 which is for compliance in the auto-loader interoperability. PSR-1 for a basic coding standard. * Only use the <?php and <?= tags. Only use UTF-8 without BOM for PHP code. * Separate side-effects (generate output, access a database etc.) and declarations. * Enforce PSR-0. * Class names must be defined in StudlyCaps. * Class constants must be defined in upper case with underscore separators. * Method names must be defined in camelCase.
PSR-2 is for the logger system viz: debug, info, notice, warning, error, critical, alert and emergency.
*Improved indexers, Magento 2 performance toolkit, Varnish caching integration, and Full page caching are all aimed to provide better performance and scalability
A more intuitive admin backed reduces the learning curve and saves speed in finding required task.
Clean slate! A blank theme without no customization lets developers start creating new themes adding the required features one at a time. This not only enhanced the speed of theme development, but also reduces the learning curve. We should see more and more theme developers doing Magento 2 themes.
Magento 2 comes with a Migration Tool that helps us to migrate from Magento 1.9.X.X to Magento 2 relatively easy. Using this tool one can migrate EAV, Attributes, Log, Shop Settings, Customers, Orders, Catalogs and Categories. Basically Magento 2 makes migration of data and settings easy.
Modular architecture of Magento 2 lets us to breakdown the subsystems and hosting on different servers optimized for specific usage/load types. Catalog, Shipping, Sales, Checkot and Payment sub-systems can be separately optimized for increased performance, scalability and security.
These are sections in the testing framework for integration, units, static environments, functional areas, and performance. This can reduce the bug fix iterations while making testing relatively easier.
Schogini assures 24x7 - 6 hour turn around ticket response time and 24 hour Email response time (firstname.lastname@example.org)