launchpad development|
Size: 2504
Comment: Update link.
|
Size: 3155
Comment: Mention production goal.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| '''''Note:''' Launchpad does not work on [[https://wiki.ubuntu.com/KarmicKoala|Karmic]] yet! There is currently a hard dependency on python2.4, but we aim to fix this before Karmic is released. Launchpad developers are currently using [[https://wiki.ubuntu.com/JauntyJackalope|Jaunty]]. If you wish to live on the bleeding edge, there are some initial notes at [[LaunchpadOnKarmic]], but do not expect this to be fully working yet.'' | <<Anchor(system)>> = System Requirements = Building and running Launchpad requires a computer running [[http://www.ubuntu.com/|Ubuntu]]. Launchpad can now run on beta [[https://wiki.ubuntu.com/KarmicKoala|Karmic]], the version of Ubuntu scheduled for release on 29 Oct 2009. 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 37: | Line 41: |
| For advanced running see [[Code/HowToUseCodehostingLocally | Advanced running of Launchpad]] |
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. Launchpad can now run on beta Karmic, the version of Ubuntu scheduled for release on 29 Oct 2009.
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 have 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 Postgres.
WARNING! |
DO NOT run the database setup script below if you use Postgres for anything other than Launchpad! Running the script will destroy any Postgres databases on your system. (see DatabaseSetup for more) |
||
$ ./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
For advanced running see Advanced running of Launchpad
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).
Open up your local webbrowser and go to
Now try logging into your locally-running Launchpad, using the default username and password:
username: admin@canonical.com password: test
Stopping
You can stop Launchpad by doing a 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
/RemoteAccess -> How to setup so you can use it from another PC
