Search results

  1. G

    Fibers (rails, ruby 1.9) and SAPI

    Here is exemple app http://github.com/igrigorik/async-rails/ There is already mysql async gem, rack async (rack-fiber_pool) and http async. I'm wonder if we can join prefork with fibers (lets say 4 rails process all supports async request).
  2. G

    Fibers (rails, ruby 1.9) and SAPI

    Did you plan support Fibers in sapi? What is Fibers? It is async no- blocking rails instances that can handle more that 1 request at the same time (no threads!). More info you can get here: http://blog.envylabs.com/2010/07/no-callbacks-no-threads-ruby-1-9/ I tested it with Thin and...
  3. G

    Server don't restart if new request comming

    maybe this is not bug - but when client establish connection with server and send request quicker that keep-alive connection timeout server will not shutdown lest say our server has 5 second timeout and 2000 max request. in worst scenario server will restart after 2,7h. Maybe it is...
  4. G

    Rails 3.0 lsapi runner

    you welcome :)
  5. G

    Rails 3.0 beta & ruby 1.9.1 don't works

    I wrote my own rails3 runner: http://www.litespeedtech.com/support/forum/showthread.php?t=4025
  6. G

    Rails 3.0 lsapi runner

    For all who want run rails 3 with litespeed web server i wrote rails3 runner http://github.com/madmax/lsws-rails3-runner it works good with ruby 1.9.x (it should works with ruby 1.8 but i didn't tested it yet) It won't works with older rails (without config.ru)
  7. G

    ruby lsapi removes RAILS_ROOT value from ENV

    i think RAILS_ROOT shouldn't be removed. Also RAILS_ROOT isn't set once when ruby starts? By the way i wrote Rails3 runner: http://github.com/madmax/lsws-rails3-runner
  8. G

    ruby lsapi removes RAILS_ROOT value from ENV

    after include lsapi it removes RAILS_ROOT varible from ENV why? also why include lsapi chdir to rails_root? rails_runner do this! (i think it is bad design that include makes something like that) require "rubygems" ENV["RAILS_ROOT"] = "./" puts "BEFORE: #{ENV["RAILS_ROOT"]}" require...
  9. G

    Rails 3.0 beta & ruby 1.9.1 don't works

    it is in deprecation folder that meen it probably will be removed in next version :) Don't know try install ruby 1.9.1 (with rvm is so easy) and rails 3 beta http://railscasts.com/episodes/200-rails-3-beta-and-rvm
  10. G

    Rails 3.0 beta & ruby 1.9.1 don't works

    Currently lsapi can't run rails 3 beta i fixed some issuses but still get errors. Here is my railsrunner (only for test with hardcoded paths): #!/usr/bin/env ruby ENV['RAILS_ROOT'] = "/Users/madmax/Sites/rails3-test" Dir.chdir(ENV['RAILS_ROOT']) #require 'lsapi' require...
  11. G

    my rails runner

    i didn't checked yet but when i will test new loader (with include boot.rb) i will inform you.
  12. G

    my rails runner

    I think there is 1 litle problem with RailsRunner: require 'active_support' require 'action_controller' if you include config/boot i think they are arledy loaded if not it will load newest version of this libs even application runing older rails (if there is 2 rails version...
  13. G

    [RESOLVED] Env['http_x_forwarded_for']

    my foul my test proxy dont pass this varible. This bug can be closed.
  14. G

    [RESOLVED] Env['http_x_forwarded_for']

    Litespeed don't set HTTP_X_FORWARDED_FOR varible in ENV (ruby lsapi 4.0) in php lsapi all works ok.
  15. G

    [RESOLVED] Can i use litespeed without cpanel?

    also you can install phpmyadmin for database managment.
  16. G

    [RESOLVED] Restart problem (old server isn't killed)

    Ok after few days tests all working ok :)
  17. G

    Ruby 1.9

    mistwang thanks i will test it :)
  18. G

    Ruby 1.9

    I think it is good time to start working with lsapi support ruby 1.9.1
  19. G

    [RESOLVED] Restart problem (old server isn't killed)

    Hmm right i set it to 0 strange :) of corse parent should to it i think. But i will test it with completly removed LSAPI_PPID_NO_CHECK
  20. G

    [RESOLVED] Restart problem (old server isn't killed)

    still sometimes all lsapi process arent turned off. Why server exit before it checkc that all sapi process are killed? (i meen root process not www with not have rights to kill sapi process) This is lived lsapi process: root@core2:/opt/lsws/fcgi-bin# truss -p 68635...
Top