Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Stop tracking database.yml files #537

Merged
merged 4 commits into from Oct 19, 2012

Conversation

Projects
None yet
2 participants
Contributor

josiahivey commented Jul 16, 2012

This stops tracking the database.yml files so that tests can be run by a contributor. It renames the currently tracked files with a .example extension.

Is there a section in the documentation that covers contributing? If so, I can add the necessary steps for renaming the .yml files.

Thanks!

Collaborator

peakpg commented Jul 19, 2012

Thanks, I will take a look at this. There is no real 'contributor' page right now, which probably makes it hard for folks to get started. However, adding a rake task that renames the .yml files would be hot.

I tend to optimize the set up for the project mostly for my own happiness currently, but I'm definitely interested in making the project easier for other to get started on.

Contributor

josiahivey commented Jul 21, 2012

A rake task sounds like a fantastic idea! I'll check into that.

Contributor

josiahivey commented Aug 20, 2012

I've added a rake task called test:setup that will copy over the example files.

I also have it copying over database.yml in test/dummy, as this was required for me to run the tests. The file itself says not to edit it, but that doesn't seem to be correct. Should that warning be removed?

@peakpg peakpg merged commit 33410e7 into browsermedia:master Oct 19, 2012

Collaborator

peakpg commented Oct 19, 2012

Thanks Josh,

I ended up tweaking the rake file to allow users to create the database.yml for their database. I.e. rake project:setup[mysql]. I also added some checks to make it less confusing for users that first clone the repo to remind them what they need to do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment