Search results

  1. S

    4.0 road map

    Feature request I've been meaning to ask for this for a long time, but it would be awesome to have some kind of a RESTful interface into the admin tool. Even if it was just the ability to add/remove sites from the templates that would be great. I just finished writing a little script that...
  2. S

    Rails staging environment

    I had it set in both places, but I had assumed that staging in LiteSpeed translated to test in Rails. Once I changed that in the database.yml file and renamed the test.rb file to staging.rb everything worked fine.
  3. S

    Rails staging environment

    I'm trying to get Rails running in the new staging mode and I get the following error: [config:server:rails] invalid value of <railsEnv>:2, use default=1 In case this was dependent on the ruby-lsapi I upgraded that to 2.9. Any idea why this isn't working? This is the standard version of...
  4. S

    Keep ruby RailsRunner.rb's running all the time?

    I'm looking to do something similar, but changing the LSAPI_MAX_IDLE environment variable makes no difference. I've tried setting it to an hour and setting it to zero and either way it goes away after 60 seconds.
  5. S

    customize access log format

    I see in the notes for RC2 that you have the ability to customize the access log format. Would that allow me to stick cookie information in the log file? If so what does the configuration for that look like?
  6. S

    Admin tool broken in RC1 Mac PPC?

    Just thought I'd pass this along. There seems to be something wrong with the admin tool in RC1 Mac PPC version. I do a fresh install and go to http://localhost:7080/ and it redirects to /admin/index.php but the page is completely blank. Doing a view source returns an empty page as well. I tested...
  7. S

    Logging a cookie to the access logs

    I know that our Customer Insight Group would love to see this feature. I just did our 2007 budget that included two Litespeed Enterprise licenses so the timing would be good if it made it into 3. :)
  8. S

    Logging a cookie to the access logs

    Thanks mistwang. So I take it it's not on the radar for Enterprise 3?
  9. S

    Logging a cookie to the access logs

    Hi all. Our CIM group wants to log a unique cookie to the access logs to better track unique visitors. Creating the cookie is not a problem but I don't see a way put this cookie in the access logs with Litespeed. Is it possible?
  10. S

    Problem installing ruby-lsapi

    Thanks for all your help! I was able to compile it and finally get it working with gcc 3.4.5 from blastwave. Everything is working great now. Thanks again!
  11. S

    Problem installing ruby-lsapi

    I'm using a freshly created rails app. I only changed the database.yml file to point to a real database to rule out that the app wasn't hanging because it was trying to use a database. I upped the default time outs to 120, but everything else is the default settings and a fresh rails app should...
  12. S

    Problem installing ruby-lsapi

    Ok, I've tried installing Ruby and gems from source and still no luck. I'm determined to make this work because I really don't want to use Apache/Mongrel or even LS/Mongrel for that matter. Quick recap on where I am in my latest attempt. I installed Solaris 10u2. I installed the Sun compiler...
  13. S

    Problem installing ruby-lsapi

    Ok, I figured out the compile problems. It looks like it was because I was using Blastwave ruby and gem packages. I grabbed the Sun compiler and everything compiles fine now. I've been away from Solaris for a long time so I'm slowly getting back up to speed. I'm still having problems running...
  14. S

    Problem installing ruby-lsapi

    Looks like it's using the GCC compiler package I installed. It's gcc 3.3.2 on Intel Solaris. Should I be using something else and if so how do I set that when doing a gem install?
  15. S

    Problem installing ruby-lsapi

    I'm having problems installing ruby-lsapi on Solaris 10. When I run 'gem install ruby-lsapi' I get the following errors: Building native extensions. This could take a while... In file included from /usr/include/sys/signal.h:34, from /usr/include/signal.h:26...
Top