This happens to me aswell.
Jon Hancock escribió:
> Here's the head of my development.rb, standard stuff:
>
> Merb.logger.info("Loaded DEVELOPMENT Environment...")
> Merb::Config.use { |c|
> c[:exception_details] = true
> c[:reload_templates] = true
> c[:reload_classes] = true
> c[:reload_time] = 0.5
>
> thanks, Jon
>
> On Sep 25, 3:00 pm, bruce zuo <[email protected]> wrote:
>
>> I am not on both edge and 1.9.1, but it sounds like the params in your
>> development.rb, could you check those :reload_* values?
>>
>> --Bruce
>>
>>
>>
>> On Fri, Sep 25, 2009 at 12:54 PM, Jon Hancock <[email protected]> wrote:
>>
>>
>>> I've been using merb edge with ruby 1.9.1 for more than a month now.
>>> Every change I make to a controller causes me to have to kill merb and
>>> restart.
>>>
>>> To be more clear, after I make even a minor edit to a controller
>>> (including for example, adding a comment), and then hit the page again
>>> with my browser, I get this browser error: "Firefox can't establish a
>>> connection to the server at localhost:4000." No error in the merb
>>> console, I have to kill the process and start again.
>>>
>>> I'm using thin and start my dev process as: merb -a thin
>>> My dependencies are minimal, I'm not using an ORM, so all dm stuff is
>>> commented out. I'm not using the password slice, so all those
>>> dependancies, including merb-slices, are commented out
>>>
>>> Anyone else have this problem, this is really getting tiresome?
>>> thanks, Jon
>>>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"merb" 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/merb?hl=en
-~----------~----~----~----~------~----~------~--~---
