Search results

  1. M

    mailman on cPanel

    Fixed, please download 2.2.2 release again. Please let me know the result. :)
  2. M

    Problem installing LiteSpeed 2.2.1 Standard on UNIX

    You can safely ignore that warning. That's because that "Max idle time" has been configured to 300 seconds under rails tab. The server will stop the ruby processes if the application idle for that long. However, when next request cames in, the server should start up another set of ruby process...
  3. M

    Problem installing LiteSpeed 2.2.1 Standard on UNIX

    The compile error will be fixed, some C compiler is more strict about variable delaration in a function. Forgot to put in the fix for Makefile. For OCI dirver, maybe it is due to missing environment variable required by OCI driver. You can add those environment variables under "Rails" tab...
  4. M

    Ruby tab in new version

    Those are independent, the rails app created in the old way still works, the new way is much easier to use. Please take a look at our Wiki if you had not.
  5. M

    LiteSpeed on FreeBSD 6.1

    Latest release is available at http://www.litespeedtech.com/packages/2.2/lsws-2.2.2-std-i386-freebsd6.tar.gz If you are on AMD64, please install the 32bit compatible library.
  6. M

    Markaby + Litespeed LSAPI: "warning already initialized constant ENV"

    OK, I did "gem install markaby", and I have test rails application, can you please give me a brief workthrough to create a simple test case for markaby? Thanks. :)
  7. M

    Markaby + Litespeed LSAPI: "warning already initialized constant ENV"

    That warning is because LSAPI override the ENV variable, the warning message usually shows up in lsws/logs/stderr.log and can be safely ignored.
  8. M

    Problem installing LiteSpeed 2.2.1 Standard on UNIX

    Please try http://www.litespeedtech.com/packages/lsapi/ruby-lsapi-1.9.tar.gz, "gets" function has been added. Please let me know the result. :)
  9. M

    Capistrano Deployment

    Yes, it is the recommended way.
  10. M

    css errors

    Thanks for the bug report! Fixed. :)
  11. M

    Problem installing LiteSpeed 2.2.1 Standard on UNIX

    What you did is correct. I had the same problem with install-sh on solaris, just copy it manually. The problem with irb is that "gets" function is not defined with LSAPI. Will fix that.
  12. M

    LSAPI Session Problem...

    You can take a look at ruby source code hash.c, env and hash has the exactly the same interface. Those two are interchangeable and ruby code cannot tell the difference. Some ruby module just substitutes the environment array with a hash. ;)
  13. M

    LSAPI Session Problem...

    ENV['RAILS_ENV'] has been unset in LSAPI after the initialization. RAILS_ENV should be used whenever you need to reference it. You can change ext/lsapi/lsruby.c to let LSAPI keep that environment variable.
  14. M

    503 Service Unavailable

    Correct. You can back up your vhost configuration if you want to.
  15. M

    503 Service Unavailable

    Please make a fresh installation and make sure the phpinfo page works, then cutomize the configuration from there.
  16. M

    503 Service Unavailable

    If you use PHP_LSAPI_CHILDREN, you should set it to match "Max Connections" and set "Instances" to 1. Should not use PHP_LSAPI_CHILDREN and "Instances" at the same time.
  17. M

    mailman on cPanel

    That's because LSWS does not allow setuid or setgid CGI scripts by default. Mailman's CGI script is setgid. I updated the latest 2.2.2 package, please download and install again. To make mailman CGI happy, you also need to set "Force GID" under server->"security"->"CGI resource control" to the...
  18. M

    Problem installing LiteSpeed 2.2.1 Standard on UNIX

    ruby-lsapi need to be patched on solaris 8, please do the following: Please open ext/lsapi/lsruby.c, replace all "unsetenv" with "ruby_unsetenv". Open ext/lsapi/Makefile, search for "LIBS" variable, add "-lsocket -lnsl" at the beginning. Run "make install" under ext/lsapi/ directory. We will...
  19. M

    LSAPI Session Problem...

    ActiveRecord will store the session data into a backend DB, doesn't it? Is there anything suspicious in the development.log if you start the app in development mode?
  20. M

    Problem installing LiteSpeed 2.2.1 Standard on UNIX

    It probably will not happen in the near future.
Top