Actions
Refactor #96
closed
config/settings.yaml should not be under git control
Description
It is a host specific file which shouldn't be touched when you pull new changes.
Instead it should be distributed as config/settings.yaml.example
Updated by Ohad Levy almost 15 years ago
do you know of a way of removing it from git but not removing the file (for the people who do git pull?)
Updated by Martin Englund almost 15 years ago
- Assignee set to Ohad Levy
just run
git mv config/settings.yaml config/settings.yaml.example
Updated by Ohad Levy almost 15 years ago
Martin Englund wrote:
just run
[...]
what about the people who already use it? :-\
Updated by Martin Englund almost 15 years ago
I think you have to put in the release notes to re-create the settings.yaml file, as there is no way to ungit a file and still leave it (as far as I know, but I'm not a git expert, nor do I play one on TV)
Updated by Martin Englund almost 15 years ago
btw, database.yml should also not be under git control
Actions