Dreamhost deployment questions

Rails Deployment
1

Hi,

I currently host a couple apps with HostingRails, and this has generally
been okay–after a few bumps. I’ve been trying to help my brother get
his app together on Dreamhost and have run into some quirks I’d love to
have elucidated.

There seems to be an indeterminate lag between when the source code is
changed (svn update) and when (or if) the changes are reflected in the
app. It seems changing a view has an immediate effect, while changes to
controllers don’t seem to take effect for quite while (or at all).
This last change I’ve put in has not taken effect and it’s now been over
three hours.

My questions are these:

  1. wtf?
  2. I assume that there is some job that restarts the server or some such
    thing. Do es anyone know about this or where I could read about this?
    There wiki is abysmal.

It would be great is Dreamhost got their rails act together a little
better, as it would be a very inexpensive option for hosting
demonstration projects, etc. But right now, I’m uncomfortable with
them. I’d be interested to hear if Dreamhost is worth putting time and
energy into.

Any thoughts?
EB

2

pkill -9 dispatch.fcgi

On 10/21/07, Elliott B. [email protected] wrote:

changed (svn update) and when (or if) the changes are reflected in the
2. I assume that there is some job that restarts the server or some such
EB

Posted via http://www.ruby-forum.com/.

–
Jeff X.
Software Journeyman - http://gigix.thoughtworkers.org
Open Source Contributor - http://rubyworks.rubyforge.org
Technical Evangelist - http://www.infoq.com/cn/

3

Hi Jeff,

Thanks for your swift reply.

If I kill this dispatch.fcgi, the updated controllers will be reloaded?

I’ll try this.

Thanks,
EB

Jeff X. wrote:

pkill -9 dispatch.fcgi

On 10/21/07, Elliott B. [email protected] wrote:

changed (svn update) and when (or if) the changes are reflected in the
2. I assume that there is some job that restarts the server or some such
EB

Posted via http://www.ruby-forum.com/.

–
Jeff X.
Software Journeyman - http://gigix.thoughtworkers.org
Open Source Contributor - http://rubyworks.rubyforge.org
Technical Evangelist - http://www.infoq.com/cn/

4

That’s how Rails works in production mode. All classes are cached.
Views,
because they are not classes, are not cached.