On 2/18/07, Phlip [EMAIL PROTECTED] wrote:
run cd #{current_path} ; nohup ruby script/push_server
It seems that nohup didn't work from the command line, so I have a ticket
out with my ISP to see if there's a permission issue or something.
I don't claim to understand it as I don't have
Using #{previous_release}/ works perfectly for my needs. I am still
playing with the tiny_mce stuff... no luck yet.
THanks!
On Feb 16, 2:23 pm, rumplyminz [EMAIL PROTECTED] wrote:
I was just curious if you were just replying to newsgroup posts via
email, or actively going to the group to
On Feb 18, 2007, at 8:39 PM, Keith Pitty wrote:
Hi,
Having just joined the group, I have a couple of questions regarding
documentation for Capistrano.
1. I see there have been some posts this year about improving the
documentation for Capistrano. What's the latest with these efforts?
Is
On Fri, Feb 16, 2007 at 10:13:04PM -0600, Rob Sanheim wrote:
How does everyone handle security so they can do one step deploys?
For instance, right now the user we use for our deployments doesn't
have password-less sudo rights, so I still have to enter a password
for the mongrel restart.
You can lock this further down by not running mongrel_rails as root but
another user, which might be a good idea in case security holes are
found in mongrel.
Or in your code as Rails then also runs as root which you should
definitely avoid.
Jonathan
--
Jonathan Weiss
Clint,
On Feb 20, 9:17 am, ctro [EMAIL PROTECTED] wrote:
Is there a documented / recommended way to leave database.yml /
mongrel_cluster.yml, etc files out of svn?
Put your database.yml in the shared/config directory (on the server)
as database.yml.production and in the :after_code_update
This question is not exactly about Capistrano, but related.
I feel I'm about 5 minutes from getting my first Capistrano deployment
running (using mongrel cluster and the railsmachine gem). However,
every time it fails because the SVN client on the remote machine won't
connect over SSL/HTTP. Is
