[WORKFLOWS-15/34] Create README with onboarding docs

[BrunoGrandePhD]

Here's a first draft. Does anyone have feedback? Are there any other sections that I should add?

The formatted README can be read here.

[thomasyu888]

Thanks! My first look at this is it looks good!

• Is there a requirement that things must go into develop first prior to prod?
• Is nf-tower only built on prod?

[BrunoGrandePhD]

• Is there a requirement that things must go into develop first prior to prod?

@thomasyu888: I hadn't thought that far ahead yet since we're still setting things up. That said, we could make it a requirement in CONTRIBUTING.md. Once NF Tower is up and running in prod, we probably want to be conservative with changes to ensure it doesn't go down, similar to the Service Catalog model.

@tthyer: What do you think?

• Is nf-tower only built on prod?

@thomasyu888: I expect there to be an instance of NF Tower also running in develop for the reason detailed above.

[tthyer]

@BrunoGrandePhD @thomasyu888 Regarding things going into dev before prod, the way I have been thinking of this is that if you're developing a new template, it should go into dev first, and generally we may even want sample deployments in dev, such as sample-nextflow-s3-bucket. If you're just creating a new sceptre configuration, it can go straight into prod, such as bgrande-nextflow-s3-bucket.

The license allows us to have a development and production version of the tower. I would like to see the development deployment really used for development / changes, so we have a place where we're not disturbing users to make changes and updates. PHI or not, use of tower to run workflows can happen in the production account.

[BrunoGrandePhD]

I'm going to work on this once we merge other PRs that change the onboarding experience.

Depends on #62 (and a future PR where we switch from hook to CI step)