Hi there, The default recipe expects you to be able to access your web server directly from your local machine. On our web server, for security purposes, it is only possible to ssh to it through one particular ip (which is also a remote machine.) The capistrano source is so compact and tidy it looks very hackable. But rather than messing around I thought I'd ask first if anyone else has any ideas? Cheers Henry
on 2006-06-07 16:10
on 2006-06-07 18:50
Henry Turner wrote: > has any ideas? Seems doable to me. I'd probably leave the deploy task alone and create before_deploy and after_deploy tasks that did whatever you need to do. If you can tunnel through the intermediate host, this is pretty easy to do. If you have more restrictive networking rules that block port forwarding, and you can run code on the intermediate server, you could just do ssh user@particularip 'cd /path/to && rake deploy' My memory is that this will send the sudo prompt back to you, but I could be wrong about that. In some production environments, this might be the easiest way to go. -- Ray
on 2006-06-07 18:57
on 2006-06-07 19:13
I remeber having had the same problem, but I don't remember the solution. But why don't you proxy to mongrel and serve the static files with apache ? That is much easier to setup and works very well for me.
on 2006-06-07 19:35
Well, if I can't fix this problem then I may consider doing that, but for the time being I'd like find a working solution for lightTPD.
on 2006-06-07 21:19
Why would you prefer to use three things when two will do? -- -- Tom Mornini
on 2006-06-07 21:32
"Why would you prefer to use three things when two will do?" ??? Who is using 3 things? There are two options that were discussed: 1) Apache being the proxy for lightTPD 2) Apache being the proxy for mongrel At least that's how I understood the suggestion. -Steven
on 2006-06-07 22:38
On Jun 7, 2006, at 11:31 AM, Steven Hansen wrote: > "Why would you prefer to use three things when two will do?" > > ??? > > Who is using 3 things? There are two options that were discussed: > > 1) Apache being the proxy for lightTPD Lighty then passes Rails requests to FastCGI, which makes it three. > 2) Apache being the proxy for mongrel Where mongrel handles the Rails requests, making it two. -- -- Tom Mornini