Question about updating files in production / Mongrel restart

Hello,

I just completed my first real rails application. I successfully
deployed it, configured apache/mongrel clusters, etc. However, I do
need to make code changes on the site often. I noticed the only time
the change takes effect is when mongrel is recycled. Is there anyway
around that? I know best practice is to do scheduled updates...etc.
But this s a small site that will have need frequent updates. I read
up on Capistrano a bit, but it seems that part of its steps is a
mongrel restart. Is this really the only way?

Thanks!
--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-talk (AT) googlegroups (DOT) com
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe (AT) googlegroups (DOT) com
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

On Fri, Nov 6, 2009 at 5:58 PM, MJFuzz <mjaffe02 (AT) gmail (DOT) com> wrote:

Hello,

I just completed my first real rails application. I successfully
deployed it, configured apache/mongrel clusters, etc. However, I do
need to make code changes on the site often. I noticed the only time
the change takes effect is when mongrel is recycled. Is there anyway
around that? I know best practice is to do scheduled updates...etc.
But this s a small site that will have need frequent updates. I read
up on Capistrano a bit, but it seems that part of its steps is a
mongrel restart. Is this really the only way?

I don't think you have another choice if you're using mongrel,
however, I've never deployed mongrel clusters, always used passenger.
--
Leonardo Mateo.
There's no place like ~

--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-talk (AT) googlegroups (DOT) com
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe (AT) googlegroups (DOT) com
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

In production mode, the classes are all cached on load. This is for
performance reasons. In development mode, the classes are reloaded on
each request which enables you to see your changes immediately. That
being said, changes to routes or the environment files would still not
reload. Generally speaking restarting your mongrel/passenger
instances is the best approach. If you are less concerned for
performance you could run in production with caching disabled, though
I would advise against it. Even for a small site, Capistrano is
simply to setup & well worth doing. Also, dump Mongrel & use
Enterprise Ruby & passenger.... it is so much less of a headache to
manage for deploys & manages memory much better you'll appreciate the
change.

Niels


On Nov 6, 2009, at 12:24 PM, Leonardo Mateo wrote:

On Fri, Nov 6, 2009 at 5:58 PM, MJFuzz <mjaffe02 (AT) gmail (DOT) com> wrote:

Hello,

I just completed my first real rails application. I successfully
deployed it, configured apache/mongrel clusters, etc. However, I do
need to make code changes on the site often. I noticed the only time
the change takes effect is when mongrel is recycled. Is there anyway
around that? I know best practice is to do scheduled updates...etc.
But this s a small site that will have need frequent updates. I read
up on Capistrano a bit, but it seems that part of its steps is a
mongrel restart. Is this really the only way?


I don't think you have another choice if you're using mongrel,
however, I've never deployed mongrel clusters, always used passenger.
--
Leonardo Mateo.
There's no place like ~

--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-talk (AT) googlegroups (DOT) com
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe (AT) googlegroups (DOT) com
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

great! i will look at that. Thanks!

On Nov 6, 12:33*pm, Niels Meersschaert <nmeersscha... (AT) mac (DOT) com> wrote:

In production mode, the classes are all cached on load. *This is for *
performance reasons. *In development mode, the classes are reloaded on *
each request which enables you to see your changes immediately. *That *
being said, changes to routes or the environment files would still not *
reload. *Generally speaking restarting your mongrel/passenger *
instances is the best approach. If you are less concerned for *
performance you could run in production with caching disabled, though *
I would advise against it. *Even for a small site, Capistrano is *
simply to setup & well worth doing. *Also, dump Mongrel & use *
Enterprise Ruby & passenger.... it is so much less of a headache to *
manage for deploys & manages memory much better you'll appreciate the *
change.

Niels

On Nov 6, 2009, at 12:24 PM, Leonardo Mateo wrote:





On Fri, Nov 6, 2009 at 5:58 PM, MJFuzz <mjaff... (AT) gmail (DOT) com> wrote:

Hello,

I just completed my first real rails application. I successfully
deployed it, configured apache/mongrel clusters, etc. However, I do
need to make code changes on the site often. I noticed the only time
the change takes effect is when mongrel is recycled. Is there anyway
around that? I know best practice is to do scheduled updates...etc.
But this s a small site that will have need frequent updates. I read
up on Capistrano a bit, but it seems that part of its steps is a
mongrel restart. Is this really the only way?

I don't think you have another choice if you're using mongrel,
however, I've never deployed mongrel clusters, always used passenger.
--
Leonardo Mateo.
There's no place like ~


*smime.p7s
3KViewDownload

--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-talk (AT) googlegroups (DOT) com
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe (AT) googlegroups (DOT) com
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

MJFuzz wrote:

Hello,

I just completed my first real rails application. I successfully
deployed it, configured apache/mongrel clusters, etc. However, I do
need to make code changes on the site often.

Just checking: you are using decent version control, right?

I noticed the only time
the change takes effect is when mongrel is recycled. Is there anyway
around that? I know best practice is to do scheduled updates...etc.

That's not necessarily a best practice.

But this s a small site that will have need frequent updates. I read
up on Capistrano a bit, but it seems that part of its steps is a
mongrel restart. Is this really the only way?

Just about. But why should it worry you? At least with Passenger, an
app restart only takes a few seconds.

And if you're not using Capistrano yet...set it up right away!

Thanks!

Best,
--
Marnen Laibow-Koser
http://www.marnen.org
marnen (AT) marnen (DOT) org
--
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-talk (AT) googlegroups (DOT) com
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe (AT) googlegroups (DOT) com
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---