Split config from blame.yaml

Issue #3 new
Brent Tubbs
repo owner created an issue

In the beginning blame.yaml was just about telling you who pushed the site, when, and from where. Then it added in the whole deployed site config, and then started to get used for sending live configuration into the app.

I'd like to pare that back. Let's have two files on the deployed site:

blame.yaml with just the blame parts

config.yaml with just the app_config section of the site config

Comments (1)

  1. Brent Tubbs reporter

    Decided to go a different way with this. blame.yaml will disappear entirely and will be just one section of site.yaml on a deployed site. And there will be no config.yaml. So we get fewer files hanging around, and they have the same names in production as development.

  2. Log in to comment