search for: rochkind

My production server is using mongrel_rails on Ubuntu linux. With Firefox I can reach my production server with the URL: www.mydomain.com:3000/ but I can''t reach my production server with the URL www.mydomain.com/ Is there a way to configure mongrel so that I can reach my production server with the URL www.mydomain.com? -- Posted via http://www.ruby-forum.com/.

If you append an extra percent sign to a URL that gets passed to mongrel, it will return a Bad Request error. Kind of odd that "http://localhost/%" causes a "Bad Request" instead of a "Not Found" error. Here is the error from the mongrel log: HTTP parse error, malformed request (127.0.0.1): #<Mongrel::HttpParserError: Invalid HTTP format, parsing fails.>

In my continued efforts to port my rails 1.x app to Rails 2.1.2, I keep running into what appear to be ActiveRecord bugs. I am using an :include on a :has_many definition: class Request < ActiveRecord::Base has_many :service_types, :order=>''service_types.id ASC'', :include=>:service_response [...] There''s no reason this wouldn''t be supported in

Has anyone actually gotten the activerecord-sybase-adapter to work in Rails2? I can''t seem to, and can''t figure out why. I am on RedHat linux. I have the sybase client libraries installed, I have the adapter installed. After installing the patch at https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/2455-update-for-sybase_adapter#ticket-2455-4 to get a slightly

So I''ve got an ActiveRecord model pointing to a MySQL db, with an auto-serialized column ("serialize :columnName"). Thing is, MySQL, depending on how it''s configured (like, by default), has a bad habit of just truncating your data if it''s too wide for the column, with no error raised. Yeah, I can probably reconfigure MySQL and/or my AR connection to it. But

So, given a sessionID, I have need to read and write the session stored information ''manually'', from _outside_ an actual Rails request/controller. Readers, I know your first response may be to tell me I don''t really want to do that. Trust me though, I really do, it makes sense for me in my case. I know this wouldn''t work if you''re using the new cookie

Hi am a newbie to mongrel. am using mongrel cluster in my ruby application. When i start mongrel cluster it is working fine and when i stop it it says already stopped port 8000. it is giving the error as follows ********* simple selection ********* ********* selection by list ********* -A all processes -C by command name -N negate selection -G by real

Let''s start out without ActiveRecord, just to make the case. So, I have a calculation that will take a while to run in my Rails app. One doesn''t really want to just hold a HTTP connection open until it''s done, for a variety of obvious reasons. Even though everyone says "Rails isn''t thread safe", I can''t think of any reason this would be a

Hmm, one of my migrations have stopped working on #down. It still works on #up. (It''s also possible that I never tested it for #down before, and it never worked, heh.) I can''t figure out why not. Pretty simple. class WidenRequestParams < ActiveRecord::Migration def self.up change_column :requests, :params, :string, :limit => 2048 end def self.down

Looking for suggestions on following two queries. Query 1 ------------------------------ Are the two following lines of code different in Ruby / Rails ( in a *.html.erb) file. <% if @forms.count != 0 %> <!-- first code --> Vs. <% if @forms.count %> <!--second code --> @forms is an array of objects. Coming from "C" language development background, i thought

I have a Rails 1.2.3 app (due for an update, I know) running on a Mongrel 1.1.4 behind Apache 2.2.3 mod_proxy on Debian 4.0. It keeps hanging up for no reason I can tell. I have tried everything that anyone has ever hinted at being a solution for this problem: - The application doesn''t use MySQL, so setting the connection timeout won''t help. - Using AR not PStore for sessions. -

I have following code in view <% if @next_topic %> Time to show next topic <%= distance_of_time_in_words(Time.now.utc, @next_topic.time_to_show.utc) %> <hr /> <% end %> Output: Time to show next topic {{count}} days -------------------- time_to_show has following value Mon, 20 Dec 2010 12:38:00 UTC +00:00 @next_topic comes from database. I am using SQLITE. I am using

On Thu, Jun 25, 2009 at 2:07 AM, Michael Pliskin<mike at comapping.com> wrote: > Hi all, > > > > Some disclaimer first: I am a complete newbie in mongrel and this list, so > please forgive me if I say something weird. I have a problem, I?ve googled > for a solution for quite a while and failed so far, so decided to ask here. > > > > I am trying to set up my

So I''m upgrading my app from Rails 1.2.6 to Rails 2.1.2. I have a complex find statement that worked in 1.2.6 and isn''t working in 2.1.2. I think maybe this is a bug, although maybe there''s something else I could be doing to work-around it? My find statement involves: * Models in a module for namespace purposes * a join clause with raw SQL * an includes clause with

So, man, character encoding is confusing. Worse, I''m talking to a vendor-supplied database (read-only) that I did not add the data too. At least this vendor-supplied database is MySQL. So this database has some accented charactars in it. For instance, something as simple as a lowercase o with an acute accent, for example. At first, this character was not being displayed correctly in my

Does Rails recognize ";" as a query param delimiter (as reccommended by w3c)? How about "&amp;", which apache is insisting on changing all of my & delimiters to if I try to do rewrites with the query_string? Should Rails interpret these as delimiters? Does it? Thanks! -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You

So, as I''m working on migrating my app from Rails 1.2.1 to Rails 1.2.6, suddenly my database adaptor password is showing up in production log on startup. This could be because use " ActiveRecord::Base.allow_concurrency = true" (I know, nobody else does and you''ll tell me not to do it. But I''ve investigated it and it''s working for me, that''s

So the rdoc claims that a rails request object should have a headers method, right? http://api.rubyonrails.org/classes/ActionController/AbstractRequest.html ************** headers() Provides acccess to the request‘s HTTP headers, for example: request.headers["Content-Type"] # => "text/plain" ************* Sounds simple enough. But when running in development mode on the

So Rails2 provides a new BufferedLogger class that is used for logging. The old monkey-patched Logger class is deprecated. It''s nice that the new BufferedLogger doesn''t do that weird monkey patching thing, making it easier to sub-class for custom behavior and set your sub-class as the logger, etc. But oddly, BufferedLogger is not a sub-class of the Ruby logger. It''s

So I have an action that results in atom: def index ... respond_to do |format| ... format.atom { render :layout => false} end end Then I have a builder template to render the atom, called index.atom.builder. Inside this builder template, I''d like to render one of my existing html partials, to put in the atom:content element, perfectly normal atom thing to do.