On 6/30/06, Robert J. [email protected] wrote:
- Runs the unit and functional tests.
- Starts mongrel
So, I’d make a change to the migration script, and then run the
Also, you can create a script or rake task called “commit”. You’d run
this every time you check something in. This task or script would:
So, after i make a change, I run the script/reload_everything program.
When I want to commit, I run ‘rake commit’. Makes it pretty easy.
Sure, it’s pretty simple. (using postgres)
(script/reload_everything.sh is ignored by subversion, so on a fresh
checkout, a developer would copy the sample file)
echo " *** Dropping the development and test databases…"
echo " *** Creating the development and test databases… "
echo " *** Running the migration scripts…" &&
rake migrate &&
echo " *** Loading the test fixtures… " &&
rake load_fixtures &&
echo " *** Running the tests" &&
mongrel_rails start -d
(run with ‘rake commit’)
desc “Tests the files, then commits”
task :commit do |t|
check to see if there’s unadded files. If there are, I’m not
saving anything, darn it.
if (unadded_files = system “svn status | grep -v ‘.swp’ | grep
puts “There were unadded, removed, screwed up, or conflicting
system “script/reload_everything.sh && svn commit”