# Magento comes with different application (or deploy) modes to assist in
# running code properly, depending on where and when Magento is used. You
# can retrieve the currently active application mode by running:
bin/magento deploy:mode:show

# The default mode is, of course, default. This mode is more of a "demo" mode.
# Its settings are generally made to make Magento "work" out of the box with
# very little to no configuration, but this mode shouldn't really ever be used.
bin/magento deploy:mode:set default

# Development should always be done in developer mode. This disables specific
# caches and outputs errors to the browser for easier development workflow.
# Developer mode also enables code compilation processes to happen automatically
# instead of needing to manually compile files.
bin/magento deploy:mode:set developer

# Live production Magento instances will always want to run in production mode.
# This mode enables many caching levels and dramatically speeds up web requests,
# and also requires the manual compilation of generated files. It also disables
# debugging output and errors from being displayed in the browser for security.
bin/magento deploy:mode:set production

# Maintenance mode is intended to be used in production environments. This mode
# creates a var/.maintenance.flag file, which tells the Magento application to
# skip normal response processing and instead return an "unavailable" page. It
# can also be enabled in certain scenarios such as during code deployments, or
# when one wants to ensure specific code is run before a deployment occurs.
bin/magento maintenance:enable