I'm the only consumer of the application, so sqlite is just fine for me :) Here's an idea: in the development clone I can set the development database to an sqlite3 database (just a development database. nothing unusual here), but I can also make use of the "production" environment of the development clone to point to my real production database (or better: a copy of it). That way I can use (a copy
I do this too. I have a script that copies my production db to my development db so I can reproduce bugs and try new stuff using the data I use day-to-day. of) my production data to easily reproduce bugs, and check if new features will work in (my) production (testing other scenarios is still a must of course, if applicable), avoiding the need for multiple commit-push-pull cycles. (or the need to manually populate the database with more data). config/database.yml is in .gitignore, so you can edit that without accidentally committing it. That, in combination with storing *.db files outside of the git clone will make a powerful setup I think (and no need to add more stuff to .gitignore) I use mysql, so no problems with personal files in the git-tree :-) Reinier
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
