search

RBangel / weneedtowatch

0 stars 1 forks source link

Allow local configs #8

Closed McPolemic closed 6 years ago

McPolemic commented 6 years ago

Users are going to have different usernames, different passwords, different database setups. By having an untracked config/local.exs, we can allow users to override settings without having to change version-controlled files like config/dev.exs.

I've also added a config/local.exs.example that can be copied over to start configuring an install.

RBangel commented 6 years ago

Still undecided, but this feels like the wrong solution. The dev, test, and prod files should be changed for your environment. Maybe that means they should be built around env variables or maybe that means they should have .examples instead and aren't checked in... we shouldn't have a single global override.

McPolemic commented 6 years ago

I see where you're coming from but I'm not entirely sure I agree. We may set environment-specific configuration in those files and we can't rely on making changes to example files and hoping that those changes trickle back into untracked config files. I've seen this model of having an ignored local config and other projects and I think it's a good compromise between install customizability and the ability to set environment-specific configuration for project.