Problems using passenger with capistrano standard deployment pattern
0 views
Skip to first unread message
trevorrowe
Jun 4, 2008, 3:59:11 PM6/4/08
to Phusion Passenger Discussions
One of capistrano's standard patterns is to have the "current"
directory a symlink into a directory of timestamped releases. It
appears that after a deployment touching the tmp/restart.txt does not
get mod rails to retire the old application spawner and applications.
the tmp directory is global to all releases so it is being found and
removed by mod rails, but it appears in my process list that mod rails
treats the old application spawner as a different application all
together because its ACTUAL path on disk is different.
Is there any way I can send a message to passenger to let it know its
okay to kill these processes?
directory a symlink into a directory of timestamped releases. It
appears that after a deployment touching the tmp/restart.txt does not
get mod rails to retire the old application spawner and applications.
the tmp directory is global to all releases so it is being found and
removed by mod rails, but it appears in my process list that mod rails
treats the old application spawner as a different application all
together because its ACTUAL path on disk is different.
Is there any way I can send a message to passenger to let it know its
okay to kill these processes?
Reply all
Reply to author
Forward
0 new messages