Hi Doug, this is awesome. I just got it up and running in 5(!) minutes! Thanks so much for setting it up.

I did run into one hiccup, which I think might have to do with my own lack of understanding of some of the recent changes to how dbt handles profiles.

I initially received this error:

% dbt run -s simple_model --target prod 17:53:26 Encountered an error while reading the project: 17:53:26 ERROR: Runtime Error Could not find profile named 'diffle_shop' 17:53:27 Encountered an error: Runtime Error Could not run dbt 

This occurred (I think) because I've saved an environmental variable in my local ~/.zshrc file that informs dbt of the location of my profiles.yml file.

To that effect, the following line exists in my .zshrc:

export DBT_PROFILES_DIR=~/.dbt 

I included that line in my .zshrc because in (most) other contexts, I don't want dbt to automatically use the profiles.yml file in the project itself.

As a workaround to get this project up and running, I copy/pasted the contents of the project's profiles.yml into my local ~/.dbt/profiles.yml. But ideally, I would use the project's profiles.yml, because of course now the profile is not source controlled--not to mention, that's a manual step that is not documented/intuitive.

Could something be included in the README's recommended commands so that even a user who had the profile path configured as a DBT_PROFILES_DIR environmental variable (like I did) receive the profile from the project's profiles.yml? Or is it a bad/outdated practice to set DBT_PROFILES_DIR in .zshrc?