[Backgroundrb-devel] deployment issues?
Rob at AgileConsultingLLC.com
Wed Oct 25 15:23:11 EDT 2006
> ----- Original Message -----
> From:Bill Walton
> To: BackgroundRb
> Sent: Tuesday, October 24, 2006 7:58 AM
> Subject: [Backgroundrb-devel] deployment issues?
> Thanks to many of you, I've got my session management working with
> BackGrounDRb. Very cool. So now I need to deploy it. I'm on a
> shared hosting plan (at a2hosting in case that matters). Are there
> any issues I should expect to have to deal with in getting them to
> deploy the plugin? Anything special I need to do? I'm wondering
> in particular about the 'start up' steps.
> On 10/25/06, Bill Walton <bill.walton at charter.net> wrote:
> I sent the tech support folks at my host the following question:
> I need to get the BackgrounDRb plugin ( http://rubyforge.org/
> projects/backgroundrb/ ) installed for my app. Is that something I
> get you to do? Or is it something I need to do myself?
> To which they replied:
> If this is a simple gem install we can do that. Please provide the
> exact name of the gem used in the 'gem install' command. Thanks.
> How should I respond? Is there a difference between a gem and a
> plugin? Is this something I can / should do myself on a shared
> hosting platform?
On Oct 25, 2006, at 10:54 AM, Michael D'Auria wrote:
> BackgrounDRb is a plugin, which means it is specific to your app
> whereas a gem is a globally available piece of software. The best
> gem example i can give is mongrel, you install it once and use it
> with all your apps.
> This means that you will have to install the plugin yourself, what
> is your dev environment? If you develop on your local machine,
> which you should be, then you can just issue "script/plugin install
> svn://rubyforge.org//var/svn/backgroundrb" All on one line of
> course. You can follow the rest of the installation directions
> here: http://backgroundrb.rubyforge.org/. Once it is installed
> locally and working locally, you can just simply upload your
> project to your hosting provider.
> .: Michael :.
And the startup script for BackgrounDRb specifically expects:
require RAILS_ROOT + '/vendor/plugins/backgroundrb/backgroundrb.rb'
so you really don't have a choice but to install it as a plugin.
I just got a deployed BackgrounDRb working on a PowerVPS host and
needed to make RAILS_ENV=production explicit as well as adding a
'nohup' to keep the detached process running when deployed (or
restarted) through capistrano.
I just received a response from TextDrive (i.e., another shared host
environment) about my question regarding a port number to use. The
suggestion was to use a Unix-domain socket rather than a TCP socket
I need to pull the latest code from the svn and see about what kind
of patch(es) I might be able to give back to Ezra and one of them may
be to permit use of a Unix rather than TCP socket. I'll post my
solution back to the list.
Rob Biedenharn http://agileconsultingllc.com
Rob at AgileConsultingLLC.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Backgroundrb-devel