Code

Not logged in - Log In / Register

Revision 9 as of 2010-05-04 15:19:40

Clear message

This page is about how Launchpad's Code Hosting component. Please ask for help right away if you have any questions.

Launchpad Code Hosting

Launchpad hosts source code using Bazaar branches. However dealing with code in Launchpad covers many more areas than just hosting branches.

TODO: add section on why bzr exactly

Code for the web application is only part of the Launchpad codehosting system. The major sub-systems are:

Each of these subsystems also have multiple moving parts and some have other asynchronous jobs associated with them.

The codehosting overview diagram summarizes how some of these systems interact.

You can run the codehosting system locally.

The bzr client

This is what users install on their systems to use Bazaar. The bzr application is also installed on the server side for Launchpad to use to access the information in the Bazaar branches.

Parts [and responsibilities]

Connectivity to Launchpad

Connecting to the code hosting system from the outside world is done either through SSH using SFTP or the bzr+ssh protocol, or through HTTP. Apache handles the HTTP routing using a number of mod-rewrite rules.

Parts [and responsibilities]

Hosting infrastructure

This really groups together the bits around what happens once we have a branch that a user has pushed to us, and the associated jobs that get kicked off.

Parts [and responsibilities]

The web application

Code that is executed as part of the Launchpad web application. The core concepts are documented on the Code/Concepts page.

Major features

Email processing

There is also the processing of incoming email to the code.launchpad.net domain. Currently there are two main things are triggered with incoming email:

Code imports

Launchpad provides a way for users to get access to source code from other systems as Bazaar branches. (from CVS, Subversion, git and Mercurial)

Branch source code browser (loggerhead)

Launchpad uses loggerhead to provide a web view of the branch contents. We try not to have any Launchpad specific code in loggerhead itself, but instead keep that in the launchpad_loggerhead module inside our tree.