[Catalyst-dev] Setting the port in the configuration

Matt S Trout dbix-class at trout.me.uk
Thu Oct 2 01:58:14 BST 2008


On Wed, Oct 01, 2008 at 09:03:33AM +0200, Thomas Klausner wrote:
> Hi!
> 
> This was warnocked, so I'm trying again...
> 
> -- 
> #!/usr/bin/perl                              http://domm.plix.at
> for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}

> X-Sieve: CMU Sieve 2.3
> X-Spam-Status: No, hits=-1.1 required=4.0
> X-Spam-Check-By: la.mx.develooper.com
> X-SourceIP: 62.178.225.182
> From: Thomas Klausner <domm at cpan.org>
> To: catalyst-dev at lists.scsys.co.uk
> Subject: [Catalyst-dev] Setting the port in the configuration
>
> As we have some cat apps running that need to talk to each other, we'd 
> love to start them on the same port, even if we forget the --port flag 
> to ourapp_server.pl

I often make the default port 3000 + $UID
 
> port_in_config.Catalyst-Runtime-5.70.patch changes 
> Catalyst::Engine::HTTP to use the port defined in the 'Engine::Server' 
> config section. The problem with this approach is that one cannot 
> override the configured port from the commandline or environment.

The engine isn't called Engine::Server, it's called Engine::HTTP.

Adapt your patch appropriately please.

Also, you appear to have missed the tests - could you re-send with those
attached? 

-- 
      Matt S Trout       Need help with your Catalyst or DBIx::Class project?
   Technical Director                    http://www.shadowcat.co.uk/catalyst/
 Shadowcat Systems Ltd.  Want a managed development or deployment platform?
http://chainsawblues.vox.com/            http://www.shadowcat.co.uk/servers/



More information about the Catalyst-dev mailing list