similar to: [mongrel_cluster] hosting multiple web sites via apache mod_proxy_balancer

Jeff try adding to your mongrel_cluster.yml :docroot: /var/radiant/domainA.com/public -- Together we can solve any issue.

Hello all, My Rails app is logging some rather strange requests: Processing StoreController#index (for ::1 at 2006-07-03 13:18:48) [GET] Session ID: ed5e2a0e5b4b9290835a969cdd749e6e Parameters: {"action"=>"index", "controller"=>"store"} Completed in 0.08174 (12 reqs/sec) | Rendering: 0.07951 (97%) | DB: 0.00000 (0%) | 200 OK [http://127.0.0.1/]

Dear all, In the past, I''ve been successfully using mongrel_cluster following codahale setup [1]. Now I updated mongrel_cluster through gem to 1.0.2, and my previosly worked config is not working anymore. I report below a snip of one of logfile, it seems to me it is a missing gem problems, but this sounds strange to me, because my config was ok before the upgrade. Does

Hello everybody! I''m a developer from Germany trying to run RadiantCMS on a Mongrel and Apache-powered server, and the processes keep dying away. I''ve been roaming the archives hoping to find a clue to the solution to my problem, but I didn''t get very far, since mostly the given environment or error messages don''t match mine. I''m using a Debian

Looks like it''s time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.7.1 Engraving is a bugfix release that corrects two errors in the user-interface. The contents of page-parts will now maintain escaped HTML characters across saves, and the tag reference will now properly display when ''<normal>'' is selected as the page type. The

Looks like it''s time for another release of Radiant: http://radiantcms.org/download/ This is primarily a security update. A critical security vulnerability has been discovered in Rails 1.1.4 and previous versions. Rails 1.1.6 seems to fix the problem. This version of Radiant is identical to 0.5.1 apart from the Rails upgrade. It is highly recommended that you upgrade. WHAT IS

Last night I quietly rolled out the first official release of Radiant: 0.5 - Grindstone. This release was a stability release mostly targeted toward making it easy for people to download and get started with Radiant. Radiant now ships with a simple setup_database script which makes it easy to get up and running with one of three default templates. We also made it easy for people to install

I failed to package up the Zip and Tar correctly for Radiant 0.5.2. They each included Rails 1.1.5 instead of 1.1.6. I?ve repackaged the files and they should be ready for download as soon as they propagate to the appropriate servers: * http://rubyforge.org/frs/download.php/12493/radiant-0.5.2-2.tgz * http://rubyforge.org/frs/download.php/12494/radiant-0.5.2-2.zip Since Rails 1.1.5 has a

Looks like it''s time for another release of Radiant: http://radiantcms.org/download/ This release contains a few major changes as well as numerous bug-fixes and enhancements. Included in the release are Rails 1.2.5, Prototype 1.6 and script.aculo.us 1.8. Significant refactorings have been done to the admin UI Javascripts, thanks to Mislav Marohnic. The release also provides better

Looks like it''s time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.6.8 "Incise" adds a number of new features that enhance support for extensions and completes the project''s move to github. Of special note are: * Extension installer/uninstaller scripts (script/extension) and a global ''extension registry'' at

I am pleased to announce the release of Radiant 0.5.1 Gemdust: http://radiantcms.org/download/ This is primarily a security update. A critical security vulnerability has been discovered in Rails 1.1.5. It is therefore highly recommended that you upgrade immediately. Apart from the Rails 1.1.5 upgrade, this release includes a number of small enhancements. From the change log: WHAT IS

hi i am using radiant 0.8.2 , rails 2.3.4, ruby 1.8.7 and rubygems 1.4.2. and i can''t able to run my existing application. error occurred : run command for server "script/server -e production -p 3001" error: => Booting WEBrick => Rails 2.3.4 application starting on http://0.0.0.0:3001 config.gem: Unpacked gem rack-rewrite-1.2.1 in vendor/gems has no specification

Hi, I have these following configurations: Active Directory 1 = DomainA.com AD1 Primary Group = Domain Users AD1 Group 1 = Linux (member: DomainB\ad2testuser1) Server joined = linux1.DomainA.com (configured Kerberos and Winbind Samba4 from sernet) Active Directory 2 = DomainB.com AD2 Primary Group = Domain Users (member: DomainB\ad2testuser1) AD2 User 1 = ad2testuser1 note: (1)

Cheers, I''ve just published a blog post about scaling Rails with Apache 2.2, mod_proxy_balancer and Mongrel. This way you do not need another proxy server or load balancer for Mongrel. Just use Apache 2.2 and mod_proxy balancer. http://blog.innerewut.de/articles/2006/04/21/scaling-rails-with-apache-2-2-mod_proxy_balancer-and-mongrel Jonathan -- Jonathan Weiss

Hi I just setup a server (Apache 2.2, mod_proxy_balancer, mongrel_cluster) with 2 Rails applications according to this excellent Post: http://blog.codahale.com/2006/06/19/time-for-a-grown-up-server-rails-mongrel-apache-capistrano-and-you Everythings works great, but after a long inactive period (say one night), the first 3 connections allways get an Error 500 Excerpt from production.log: ...

I''m trying to setup a mongrel cluster. I''m relying on information collected from a number of sources but I''m relying heavily on http://mongrel.rubyforge.org/docs/apache.html. I have noted that a number of sources mention the necessity of having the mod_balancer module installed in Apache. However, my primary source makes no mention of this; but instead, mentions only

We are splitting our users into 2 domains(DOMAINA and DOMAINB (changed for security reason)). I am having problems getting users who log into their workstation on DOMAINA to access a samba share on DOMAINB. We are using W2K3 servers as our AD with LDAP. Samba shares on are CentOS5.1 servers. I Can anyone point me to some docs on how to set this up? I have been rumbling through google for the past

Try nginx + evented mongrel instead of apache + normal Mongrel. Maybe :) -Roger -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20070917/c6f6f43a/attachment.html

I started the mongrel_cluster and tried to use the RewriteRule to forward the requests to proxy_balancer just as the http://mongrel.rubyforge.org/docs/apache.html said. When I visited my site from a remote computer, I always got the error messages "Forbidden, You don''t have permission to access / on this server." Finally, I added the "Allow from all" property (in the

I have 2 different shares one with [Share1] valid users = @"DOMAINA+Domain Users" [Share2] valid users = @"DOMAINA+SpecialGroup" Members of the latter group cannot access Share2. No one can. #getent group |grep Special DOMAINA+SpecialGroup:x:10001:DOMAINA+User1,DOMAINA+User2,DOMAINA+User3 #wbinfo -g |grep Special DOMAINA+SpecialGroup I changed the