Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the common way of dealing with the development.sqlite3 files with VCS (in particular, git)?
If I commit this file to the VCS, will it be merged with another developer’s copy?
Or should each developer run the db:migrate task each time a new migration file is created?
The most common is to ignore this file. Moreover, we usually try to allow each developer use any database that is supported by Rails. Granted that this is not always possible, especially if there is a need to bypass ActiveRecord in some occasions. Nevertheless, for most simple applications this can be accomplished.
What we do is add these lines to .gitignore among other things we ignore:
Then we include a database.yml.example file in config, where we keep the recommended way to configure the database for the application. Developers can copy that file as their database.yml, or select a different database.