deployment documentation needs 'system requirements' section

[natehill]

you know, things like, 1) get docker...

[DiegoPino]

This is not end user documentation. This demo is for development purposes for developers and dev Ops poeple. I should not go back to that level for this type of documentation. If i do that i will end documenting what drush is, what docker compose is, how drupal works, the iiif standard, etc. There will be space for that on another repo for sure El El jue, 7 de mar. de 2019 a las 15:15, Nate Hill < [email protected]> escribió:

you know, things like, 1) get docker... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGn855LmO-szp-XpNrSMaYoftIvxwD2zks5vUXNwgaJpZM4bkBek> .

-- Diego Pino Navarro Digital Repositories Developer Metropolitan New York Library Council (METRO)

[giancarlobi]

If this can help and as I'll install following readme starting from fresh VM (Ubuntu 18.04), I can trace all history to get this demo up.

[natehill]

on step 3 in the documentation it is clearer if you say 'cd web' rather than something about moving into the esmero-web container

[DiegoPino]

Step 3 is the shell line that follows the explanation.

docker exec -ti esmero-web bash -c "composer install"

So it is effectively running composer install inside the esmero-web container, not cd web.