And for as far as I'm aware, theĭi:compile step isn't multi-threaded (yet), but there were some good performance Magento 2.1.3 we can no longer benefit from the multi-threaded staticĬontent deploy, since it produces incorrect JS translations when youĬompile multiple languages at once. On 21:09, "Pieter Hoste" : unfortunately due to a new Although the steps would probably be very similar for that scenario. This isn't about a separate build server which produces an artifact which you then need to upload to a production server. ) prefer to use, so would be ideal if the documentation tries to use a similar setup.Īs a clarification, this is about documentation for a deployment process where you execute a bunch of commands on the production server itself. The deployment directories points out is what a lot of deployments scripts ( capistrano, fabric, deployer. Then we also need to know when to put the current webshop in maintenance mode (preferable for the shortest time possible), before running the upgrade scripts and when we can disable maintenance mode again. ).Īlso some commands need to have access to the database, so we would need to know at what stage in the deployment process we need to provide access to the database (preferable as late as possible). We need to know exactly which steps (commands) we need to perform and in what order ( git clone, composer install, setup:di:compile, setup:static-content:deploy, setting up correct permissions, setup:upgrade. Not about deploying updates of your project to the production server. ![]() ![]() There already exists a page about this, but this only talks about the initial setup. I also believe Magento should write some documentation about recommended deployment scenario's to/on a production server.
0 Comments
Leave a Reply. |