0435a4c17c
Ensure specified environment is used
...
If for any reason RAILS_ENV was set to test this command will start a
Rails server with test environment:
rails s -e development
But this one will start with development environment:
RAILS_ENV=development rails s
I am not sure who is at fault here, but this ensures guard-rails will
always use the environment specified by the environment option.
2012-07-08 06:29:01 -03:00
963b9e0ab2
use SIGINT instead of KILL so the pid gets cleaned up
2012-01-30 08:20:47 -06:00
7a81802b8c
Doh! APpending -u flag instead of iincluding in default
2011-08-25 15:42:39 +01:00
585dc242d6
Added support for setting the debugger (-u flag)
2011-08-25 15:26:04 +01:00
372e2cd24a
Add custom server to options (:server => 'thin').
2011-07-12 22:59:26 +10:00
4836e968d6
slightly better runner support
2011-06-29 09:47:08 -04:00
63b9fcae98
nuke the pid file if we forcibly kill
2011-06-25 12:59:34 -04:00
d0901933c1
fix a dumb thing and another thing
2011-06-25 12:57:07 -04:00
2654061350
clean up lsof on both OSes
2011-06-20 09:14:00 -04:00
d795068894
kill -INT not kiling process on linux. switched to kill -KILL
2011-06-20 03:14:53 +02:00
a7678ef54b
timeout
2011-06-01 10:42:53 -04:00
f27e753caa
increase sleep time
2011-06-01 10:37:09 -04:00
b82b011156
lol, wasn't even taking an action in the action method
2011-06-01 10:31:55 -04:00
99d8f28d8c
more better tests
2011-06-01 10:28:32 -04:00
745d49da67
add deamonize option and start some tests
2011-06-01 10:06:35 -04:00
Michel Pavan Macedo
Darrin Holst
Joel Moss
Tim Preston
John Bintz
Sidney Burks