launchpad development|
Size: 1747
Comment: New page; takes some material from the Getting page.
|
Size: 3766
Comment: Updates
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| This page describes how to build and run Launchpad on your own machine. If you run into problems at any step, please [[Help|ask for help]] right away. | ||<tablestyle="width: 100%;" colspan=3 style="background: #2a2929; font-weight: bold; color: #f6bc05;">This page tells you how to build and run Launchpad on your own machine. [[Help|Ask for help]] right away if you run into problems. || <<Anchor(system)>> = System Requirements = '''Building and running Launchpad requires a computer running [[http://www.ubuntu.com/|Ubuntu]]. The production Launchpad.net site runs on Ubuntu 10.04 LTS. Developers mostly run 10.04 LTS, 11.10 or 12.04 LTS, but others may work.''' The recommended development configuration is Ubuntu 12.04 LTS or later running Launchpad [[Running/LXC|in an LXC container]] to minimise its impact on the wider system. If you're not running a supported Ubuntu release you might choose to use an installation of one of these Ubuntu versions within a [[Running/Schroot|chroot]] or a [[Running/VirtualMachine|virtual machine]]. We'd like Launchpad to run on other operating systems, especially [[http://www.debian.org/|Debian GNU/Linux]], so that more people can contribute to Launchpad development. If you're interested in working on Launchpad portability, please [[https://dev.launchpad.net/Help|let us know]]. Note that our focus is on getting Launchpad to build easily so more people can participate in Launchpad development. Running a stable production instance would be ''much'' harder than running a single-developer test instance, and we don't recommend it. Unlike many open source projects, we're not seeking to maximize the number of installations; our goal is to improve the instance we're already running at Launchpad.net. |
| Line 4: | Line 16: |
| == Building == Assuming you have already [[Getting|gotten the Launchpad source code]], here's how to build a pristine trunk (devel) instance. First, be in the top level of the source code: |
= Building = Assuming you've already [[Getting|gotten the Launchpad source code]], here's how to build a pristine trunk (devel) instance. First, be in the top level of the source code: |
| Line 11: | Line 23: |
| '''''WARNING:''''' ''Before you can run Launchpad for the first time, you need to set up Postgres. Running the database setup script below will destroy any Postgres databases on your system. DO NOT run this script if you use Postgres for anything other than Launchpad (see [[DatabaseSetup]] for more):'' | Before you can run Launchpad for the first time, you need to set up PostgreSQL. ||<tablestyle="width: 100%;" colspan=3 style="background: #ff0000; font-weight: bold; color: #fff;">WARNING!||'''DO NOT run the database setup script below if you use PostgreSQL for anything other than Launchpad!''' Running the script will destroy any PostgreSQL databases on your system. See [[DatabaseSetup]] for details.|| |
| Line 26: | Line 40: |
| == Running == | = Running = |
| Line 33: | Line 47: |
| This only runs the basic web application. [[Code/HowToUseCodehostingLocally|Codehosting]] and [[Soyuz/HowToUseSoyuzLocally|Soyuz]] require additional steps. |
|
| Line 35: | Line 51: |
| Now try logging into your locally-running Launchpad, using the default username and password: | Point your usual web browser at `https://launchpad.dev`, and accept the local self-signed certificate. You can log in as `admin@canonical.com` without a password. |
| Line 37: | Line 53: |
| {{{ username: admin@canonical.com password: test }}} |
|
| Line 43: | Line 55: |
| == Stopping == You can stop Launchpad by doing a '''Control-C''' in the terminal where you started it: |
= Stopping = You can stop Launchpad by hitting '''Control-C''' in the terminal where you started it: |
| Line 57: | Line 69: |
= Subpage Index = * [[/RemoteAccess]] -> How to setup so you can use it from another PC * [[/SSHProxyWebsite]] -> An easy way to view the launchpad web site on another machine * [[/Schroot]] -> Running inside a schroot environment * [[/VirtualMachine]] -> Running inside a VM. |
This page tells you how to build and run Launchpad on your own machine. Ask for help right away if you run into problems. |
System Requirements
Building and running Launchpad requires a computer running Ubuntu. The production Launchpad.net site runs on Ubuntu 10.04 LTS. Developers mostly run 10.04 LTS, 11.10 or 12.04 LTS, but others may work.
The recommended development configuration is Ubuntu 12.04 LTS or later running Launchpad in an LXC container to minimise its impact on the wider system.
If you're not running a supported Ubuntu release you might choose to use an installation of one of these Ubuntu versions within a chroot or a virtual machine.
We'd like Launchpad to run on other operating systems, especially Debian GNU/Linux, so that more people can contribute to Launchpad development. If you're interested in working on Launchpad portability, please let us know. Note that our focus is on getting Launchpad to build easily so more people can participate in Launchpad development. Running a stable production instance would be much harder than running a single-developer test instance, and we don't recommend it. Unlike many open source projects, we're not seeking to maximize the number of installations; our goal is to improve the instance we're already running at Launchpad.net.
Building
Assuming you've already gotten the Launchpad source code, here's how to build a pristine trunk (devel) instance. First, be in the top level of the source code:
$ cd devel
Before you can run Launchpad for the first time, you need to set up PostgreSQL.
WARNING! |
DO NOT run the database setup script below if you use PostgreSQL for anything other than Launchpad! Running the script will destroy any PostgreSQL databases on your system. See DatabaseSetup for details. |
||
$ ./utilities/launchpad-database-setup $USER
(Please have read the previous comment before you run the above command!)
Finally, build the database schema:
$ make schema
Running
Now you should be able to start up Launchpad:
$ make run
This only runs the basic web application. Codehosting and Soyuz require additional steps.
For subsequent builds, you can just do make run right away. You don't need to do make schema every time, and you should avoid it because it's expensive and because it will clean out any data you might have put into your test instance (through the web UI or by running other scripts).
Point your usual web browser at https://launchpad.dev, and accept the local self-signed certificate. You can log in as admin@canonical.com without a password.
Stopping
You can stop Launchpad by hitting Control-C in the terminal where you started it:
^C [...shutting down Launchpad...] $
Or you can be at a prompt in the same directory and run this:
$ make stop
Subpage Index
/RemoteAccess -> How to setup so you can use it from another PC
/SSHProxyWebsite -> An easy way to view the launchpad web site on another machine
/Schroot -> Running inside a schroot environment
/VirtualMachine -> Running inside a VM.
