Awesome thanks man. Sorry about the low balling of $30. Times are
tough here and my work has been holding paychecks for 4 weeks now.

On Nov 20, 12:52 pm, Jason Keenan <[EMAIL PROTECTED]> wrote:
> Hey there,
>
> I don't get out of bed for $30 ;) but I'll help you gratis. It sound  
> like the setup might be similar to hostmonster which is who I'm  
> hosted by so that's a good start.
>
> I've got to go to work now but I'll try to put together some info for  
> you. If it gets to it I'll help you more directly.
>
> Seeya,
>
> Jason :)
> On 21/11/2008, at 7:45 AM, [EMAIL PROTECTED] wrote:
>
>
>
> > What if I pay you like $30 to get it to do that?
>
> > On Nov 20, 12:30 pm, Jason Keenan <[EMAIL PROTECTED]> wrote:
> >> Hey there,
>
> >> You'll probably have to get this info from your provider as there are
> >> heaps of variations between hosting setups. If you have a parked
> >> domain name, ask them how you setup the domain to point to the
> >> application. I wouldn't think you'd be able to run your app on port
> >> 80 either. You'd usually run the rails app say with mongrel on a
> >> different port then proxy through apache on 80.
>
> >> It sounds like you're really new to rails and server setups. Ideally
> >> you need to do some research. Search the knowledgebase of your
> >> provider to see how to setup a rails app. Make sure you know how to
> >> get things running on your local machine first and work through some
> >> of the issues there. Search through the google groups archives to see
> >> if your questions have been answered there.
>
> >> If all else fails, give a thorough description of your hosting
> >> provider so we can give more accurate tips.
>
> >> Have fun :)
>
> >> Jason
> >> On 21/11/2008, at 7:08 AM, [EMAIL PROTECTED] wrote:
>
> >>> Uploaded passenger to my root, but now I have a 500 error on my root
>
> >>> On Nov 20, 11:04 am, "Nicholas Van Weerdenburg" <[EMAIL PROTECTED]>
> >>> wrote:
> >>>> The way it normally works is your request a port, they give it to
> >>>> you (say
> >>>> 4005).
> >>>> You run rails on that port, and then your proxy apache or another
> >>>> webserver
> >>>> to point to it. Either proxy or use mod_rewrite. Make sure you
> >>>> start the app
> >>>> using mongrel and not webrick. Mongrel is the standard now, so you
> >>>> should be
> >>>> fine.
>
> >>>> Search on "deploying rails to joyent" or other to see
> >>>> instructions. They may
> >>>> be similar to your hosting company (who I am assuming doesn't
> >>>> regularly host
> >>>> rails apps).
>
> >>>> Dreamhost uses a new deployment means called "Passenger" which
> >>>> makes it very
> >>>> easy.
>
> >>>> Regards,
> >>>> Nick
>
> >>>> On Thu, Nov 20, 2008 at 1:59 PM, [EMAIL PROTECTED] <
>
> >>>> [EMAIL PROTECTED]> wrote:
>
> >>>>> My hosting company is saying it can't be on port 80. I'm  
> >>>>> willing to
> >>>>> pay to get this to work on my root domain
>
> >>>>> On Nov 19, 9:23 pm, "Steven A Bristol" <[EMAIL PROTECTED]>
> >>>>> wrote:
> >>>>>> On Thu, Nov 20, 2008 at 12:14 AM, [EMAIL PROTECTED]
>
> >>>>>> <[EMAIL PROTECTED]> wrote:
>
> >>>>>>> Sweet man, thanks!!
>
> >>>>>>> SO I did the right thing by removing the :3000 on my domain in
> >>>>>>> the rb
> >>>>>>> files?
>
> >>>>>> The urls in the config file are for writing urls in a certain
> >>>>>> part of
> >>>>>> the app. If you are running dev mode on port 80, then removing
> >>>>>> it is
> >>>>>> the right thing to do. But you should be running in prod mode on
> >>>>>> port
> >>>>>> 80, and dev mode on port 3000. Try reading a tutorial on rails
> >>>>>> to see
> >>>>>> how it works. Does anyone know a good one?
>
> >>>>>> steve
>
> >>>> --
> >>>> Nicholas Van Weerdenburg
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Lovd by Less" 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/lovdbyless?hl=en
Who loves ya baby?
-~----------~----~----~----~------~----~------~--~---

Reply via email to