If you're using a shared hosting account, all the necessary infrastructure
should already be in place for you.  See the wiki for information about
deployment.

http://wiki.dreamhost.com/Rails
http://wiki.dreamhost.com/Passenger

If you're running a VPS, it's not clear what's installed out of the box, so
you'd need to check to see that Ruby, Rails and some deployment platform are
there.  A quick check from the command line should tell you everything you
need to know.  If you need a guide to setting up, Slicehost did some good
step-by-step walkthroughs for their customers.  I know you're not on
Slicehost, but the same principles should apply.

http://articles.slicehost.com/2009/2/2/ubuntu-intrepid-mod_rails-installation
http://articles.slicehost.com/2009/2/2/ubuntu-intrepid-using-mod_rails-to-serve-your-application
http://articles.slicehost.com/2009/2/27/ubuntu-intrepid-mongrel-and-mongrel-cluster
http://articles.slicehost.com/2009/2/27/ubuntu-intrepid-apache-rails-and-mongrels
http://articles.slicehost.com/2009/3/11/ubuntu-intrepid-nginx-rails-and-mongrels


On Thu, Jun 25, 2009 at 9:11 PM, Hassan Schroeder <
[email protected]> wrote:

>
> On Thu, Jun 25, 2009 at 12:05 PM, Mr. Watson<[email protected]> wrote:
> >
> > Its at http://www.dreamhost.com on a Debian Linux server
>
> ? What is?
>
> The question is: do you have an existing application that you want
> to deploy? If so, where is that application's source code?
>
> But as suggested, reading up on capistrano would probably be a
> good start, along with googling 'rails deployment'.
>
> --
> Hassan Schroeder ------------------------ [email protected]
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to