There is no documentation about deploy commands queue and share folders and files

[luckyraul]

have a look magento/magento2#2423

I've read this and do not understand your question. Can you clarify and give an example?

[luckyraul]

Which folders and files should be shared between releases(for example for m1 var, media and app/etc/local.xml are shared) and how and what order should I use bin/magento setup commands during rollout release

[buskamuza]

Hi @luckyraul ,

could you, please, clarify what do you mean under "folders/files shared between releases"? Are those storing user data?

[luckyraul]

Usually it is everything that not changed between releases

For instance, I already know that pub/media and app/etc/env.php should be shared

/var/www/example.com/     # The deploy_to path
 |-  releases/              # Holds releases, one subdir per release
 |   |- 1/
 |   |- 2/
 |   |- 3/
 |   '- ...
 |-  shared/                # Holds files shared between releases
 |   |- logs/               # Log files are usually stored here
 |   `- ...
 '-  current/               # A symlink to the current release in releases/

[hostep]

Hi

I also believe Magento should write some documentation about recommended deployment scenario's to/on a production server.
There already exists a page about this, but this only talks about the initial setup. Not about deploying updates of your project to the production server.

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, ...).
Also 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). 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.

The deployment directories @luckyraul points out is what a lot of deployments scripts (capistrano, fabric, deployer, ...) prefer to use, so would be ideal if the documentation tries to use a similar setup.

As a clarification, this is about documentation for a deployment process where you execute a bunch of commands on the production server itself. This isn't about a separate build server which produces an artifact which you then need to upload to a production server. Although the steps would probably be very similar for that scenario.

Thanks!

[erikhansen]

@xcomSteveJohnson I agree with @hostep that the devdocs should be updated to include the recommend order of steps to deploy. It might also be useful to link to community projects that can facilitate production deployments, such as @davidalger's capistrano-magento2 Gem.

Whoever is writing this documentation may want to reference the sequence of commands in the capistrano-magento2 scripts: https://github.com/davidalger/capistrano-magento2/blob/master/lib/capistrano/tasks/deploy.rake#L14

[maderlock]

As usual we're trying to work this out ourselves but it is a lot more difficult to get working than with Magento 1 which in very well understood by this point. c.f.
http://magento.stackexchange.com/questions/102144/magento-2-deployment-process
http://magento.stackexchange.com/questions/124166/order-of-magento-2-deployment-tasks

Tracking with internal issue MAGETWO-55366.

Expect some questions from me as I get started.

[erikhansen]

@xcomSteveJohnson I'd be happy to answer questions as you have them.

[maderlock]

Ditto. We have our first production site going live next week and we've reverted to manual commands due to uncertainty over ordering of commands. Great to see some movement on this.