Search results

Unfortunately, you idea does not work. :( The solution is pretty simple, like what I suggested in the referred thread, you can chmod 0750 instead of 0755, and add "nobody" user as a member of the dedicated group of that user. this way, only "nobody" user can read that user's directory, other...

This issue will be addressed in 2.2.5 release.

Glad you find the solution yourself. :)

You can just add "Rails" context with URI "/myrailsapp/", if you application has been configured to work properly under that URL, then it should work. You should instanciate the vhost configuration if you use the template, then change or add the "Rails" context.

Location cannot be blank for static context, if you check your error log, it should complain that, you need to create "admin" directory if it does not exist under public/ folder, justa empty directory is ok, then use value "$DOC_ROOT/admin/" or just "admin/" for the location. Accessible should...

Yeah, SSL v3.0 has to be checked. :)

You can install zlib from source code, then install ruby 1.8.4 or 1.8.5 from source code.

Only the last require directive is effective I think.

/opt/lsws? You need to figure it out! ;)

lsws/logs/stderr.log. If you see "warning: already initialized constant ENV" then the ruby lsapi has been working properly. if you see "fork() failed", you still need to raise the "Process soft/hard limit" to maybe "100".

Is there anything logged in stderr.log? You can try raise "Process soft/hard limit" under "Rails" and "security" tab, see if it help.

No, ruby-lsapi does not. when you count number of processes, all processes running under that user should be included. Please check the number of processes running under the same user when 503 happens.

I think 503 is the result of this error message. all the others are normal. Make sure you ruby-lsapi installation is up-to-date. Double check "Process soft/hard limit" under both "security" and "Rails" tab, those should be set high enough, I think the fork() failures are caused by this.

Please make sure "ruby path" has been set properly, "Memory Soft/Hard Limit" and "Process Soft/Hard Limit" has been set high enough under both "Rails" and "Security" tab. If you server is reachable over internet, I can take a look for you.

You can try a default Rails application without DB involved first. run in development mode and check Rails' log file as well. Also, you need to pay attention about the "Process Limits" and "memory limits" under "Rails" tab as well as "security" tab, increase them to a higher value. LSAPI is...

If you let LiteSpeed to use Apache httpd.conf, it should work fine with the same apache configuration. If you using LiteSpeed configuration, you need to creat a vhost and add redirect context for URL"/", and create listener to vhost mapping on "*".

lsws/admin/conf/admin_config.xml. :)

rewrite rules in .htaccess are slightly different from rules at vhost level. The rewrite base (directory path) has been removed for rewrite rules in .htaccess. You need to modify those rewrite rules to take care of this. try something like RewriteRule ^(.*)/$ $1/index.html [QSA] RewriteRule...

You can just turn on .htaccess support, the rewrite rules in public/.htaccess should take care of it.

Yes, you need to rewrite the url. :)