Document ISLE - "installation" next steps

[rosiel]

We have a very simple "how to launch ISLE DC" documented. What's next? What would enable people to be able to move forward?

e.g.

• what are the reasons why I should not use the existing 'make dev'-based docker-compose script as "prod"?

[rosiel]

e.g. (thanks @noah in the kick-off call)

• "How do i move data between remote instances?"
• "how do i quickly load a default dataset?"

We also realized we use "dev" and "staging" and "prod" as words that have a lot of (personal, internal) meaning, so it might be useful to hold off on those terms, and be more specific when drafting initial documentation of what the property is that you're referring to - e.g. "a drupal that is accessible by the wider internet" is a more useful description than "prod" or (depending on your config!) an "other" configuration.

From Nigel - how will we release docker instances and tag them so that people who "have customized docker compose" don't break everything "if they use latest"

[how are we being deliberate in our use of] git tags? docker image tags? drupal versions? How do they relate? How do you update if you have already launched yourself an ISLE?

How do you "upgrade" an existing ISLE, and what kinds of things might it break?