Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Catalyst: Dev

Setting the port in the configuration

 

 

Catalyst dev RSS feed   Index | Next | Previous | View Threaded


domm at cpan

Oct 1, 2008, 12:03 AM

Post #1 of 3 (1121 views)
Permalink
Setting the port in the configuration

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$_.$/}
Attachments: message-rfc822.eml (6.69 KB)


andy at hybridized

Oct 1, 2008, 7:28 AM

Post #2 of 3 (1044 views)
Permalink
Re: Setting the port in the configuration [In reply to]

On Oct 1, 2008, at 3:03 AM, Thomas Klausner wrote:
>
> Hi!
>
> 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

Would it not be easier to just set the CATALYST_PORT environment
variable in ~/.profile or similar?

_______________________________________________
Catalyst-dev mailing list
Catalyst-dev [at] lists
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev


dbix-class at trout

Oct 1, 2008, 5:58 PM

Post #3 of 3 (1030 views)
Permalink
Re: Setting the port in the configuration [In reply to]

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>
> To: catalyst-dev [at] lists
> 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/

_______________________________________________
Catalyst-dev mailing list
Catalyst-dev [at] lists
http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst-dev

Catalyst dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.