• Immutable Page
• Info
• Attachments
• More Actions: Raw Text Print View Render as Docbook Delete Cache ------------------------ Check Spelling Like Pages Local Site Map ------------------------ Rename Page Delete Page ------------------------ Subscribe User ------------------------ Remove Spam Revert to this revision Package Pages Sync Pages ------------------------ Load Save SlideShow

These instructions assume that you already have Launchpad working for local access, and now you want it to be accessible from other machines on the same LAN.

IP Addresses

A full Launchpad development setup requires two IP addresses on the local machine, on which to run two HTTPS listeners - one for main Launchpad, and one for Loggerhead (code browsing) of private branches. As most developer workstations have only one non-local IP address, and as the second one is only required for Loggerhead on private branches, you may well not bother to set up an additional IP address. If you do want to do this, identify a suitable IP address, and add it to your machine's network configuration now.

Amending the Apache configuration

These instructions assume that you are using the Ubuntu packaged Apache 2.2 in Intrepid or later. Hardy users see the "Notes for Hardy" subsection.

• Delete the NameVirtualHost 127.0.0.88:80 line

• We are assuming that the line NameVirtualHost *:80 appears precisely once elsewhere in your Apache configuration - it should be present in /etc/apache2/ports.conf by default, check this is true

• Change all <VirtualHost 127.0.0.88:80> lines to <VirtualHost *:80>

• Change the <VirtualHost 127.0.0.88:443> line to <VirtualHost _default_:443>

• If, as mentioned above, you are opting for the simple option of just using one IP address:

  • Change the <VirtualHost 127.0.0.99:80> line to <VirtualHost *:80> too

  • Comment out the entire <VirtualHost 127.0.0.99:443> block

• Or, if you did allocate a suitable second IP address:

  • Change the <VirtualHost 127.0.0.99:80> line to <VirtualHost a.b.c.d:80>

  • Change the <VirtualHost 127.0.0.99:443> line to <VirtualHost a.b.c.d:443>

• Change all the Allow from ... lines to admit whatever address range you want

Restart your Apache server.

Notes for Hardy

• The NameVirtualHost *:80 line does not appear in /etc/apache2/ports.conf but instead NameVirtualHost * appears in /etc/apache2/sites-available/default. Delete it from there and add NameVirtualHost *:80 to ports.conf. As a consequence of doing so you'll probably have to update any other <VirtualHost *> sections in your config to say <VirtualHost *:80>.

Amending the hosts file

When you ran rocketfuel-setup, your /etc/hosts file was configured with many launchpad.dev DNS names mapped onto a pair of local IP addresses. Change them both to the non-local IP address of the machine running the development Launchpad. Or, if you did allocate a second IP address, change 127.0.0.88 to the main IP address of the machine, and change 127.0.0.99 to the second IP address you allocated.

You'll need to copy these /etc/hosts lines into the /etc/hosts file of every other machine you want to access the development Launchpad instance.

If some of those other machines run Windows, it may be helpful to know that the Windows equivalent of /etc/hosts is located at C:\WINDOWS\system32\drivers\etc\hosts.

That's it!

If you did everything above, you should new be able to access https://launchpad.dev/ in a web browser on a suitably configured remote computer.