Clarify how to set up dev, prod, ci environments

[dbeatty10]

Contributions

• [X] I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

During this conversation, I wanted to point the user to where they could learn how to set up their profiles.yml and environment variables to achieve separate development environments per developer (via different database schemas).

I was surprised that there wasn't a single webpage page in the docs that would serve as a "one-stop-shop" for setting this up. I suspect part of the reason is that dbt Cloud doesn't allow direct configuration of profiles.yml.

My first attempt to compile the relevant information is in my reply here: https://github.com/dbt-labs/dbt-core/issues/7218#issuecomment-1485072444

What part(s) of the page would you like to see updated?

Making all of the following information available or reachable from the same page would be an improvement:

• dbt's recommendation of separate schemas per developer
  • acknowledgement of many other approaches to separate environments:
    • Separate databases, schemas, or accounts
    • Alternative separation of environments
• Differences in setup for Cloud versus Core
  • In Core, how to make use of environment variables within profiles.yml
    • How the developer should configure their own environment variables
    • How environment variables can be configured in CI or production environments
    • Optional call-out: relation to twelve-factor app methodology
• How dbt generate a model's schema name by default (and options for advanced configuration via a custom macro)
• How to separate environments at the database or account or hostname levels (rather than via schemas)

Additional information

No response

[mirnawong1]

Tagging @matthewshaver as it relates to @sdurry 'a recent slack post

[mirnawong1]

I'm also addressing the environment variables bit with the core to cloud guide