Launchpad itself

need a configurable way of telling codebrowse which port to run on

Bug #667322 reported by Tom Haddon
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
High
Unassigned

Bug Description

As part of RT#40479 we're trying to set up load-balanced codebrowse instances. However, to do this, we'd need to be able to run multiple instances on the same server on different ports. From what I can see this is currently hard coded somewhere. Can someone let us know what variables to pass to the appropriate script(s) so that we can configure which ports this runs on?

Tom Haddon (mthaddon)
tags: added: canonical-losa-lp
Revision history for this message
Robert Collins (lifeless) wrote :

I'm setting this as high to match the priority of the RT ticket. Its probably pretty simple, but I haven't looked at the code [yet].

Changed in launchpad-code:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

It's set in the config as config.codebrowse.port. If an env var override is more appropriate, that would be trivial to change.

Revision history for this message
Robert Collins (lifeless) wrote :

I've setup a new config for this, it was using 'production' and there were other things to change.

Changed in launchpad-code:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.