Creating static files and caching them has a greater performance impact than generating them using the static files creation tool. However, default mode is not optimized for production because of the adverse performance impact of static files. The default mode enables you to deploy the Commerce application on a single server without changing any settings.
See Deploy the Docker environment in the Cloud Docker for Commerce guide. If you use Cloud Docker for Commerce as a development tool, you can deploy your cloud infrastructure project in a Docker environment in developer mode, but performance is slower because of additional file synchronization operations. See Deployment process in the Commerce on Cloud Infrastructure guide. Otherwise, the application remains in production mode.
Adobe Commerce on cloud infrastructure automatically runs the application in maintenance mode during a deployment, which takes your site offline until the deployment is complete. Because of the read-only filesystem, you cannot change modes in the remote cloud environments. There is no need to manage the application modes for a cloud infrastructure project.
#Magento 2 devdocs deployment how to
See Set the operation mode to learn how to manually change the Adobe Commerce operation modes. Prevent access to a site while performing updates and configurations. Ideal for development when extending or customizing the Commerce application.ĭeploy and run the Commerce application to a production system. You can run the Commerce application in any of the following modes: Mode nameĭeploy and run the Commerce application on a single server without changing settings.
0 kommentar(er)
