• Archives

  • Categories:

Local LoCo Team Portal Install

At the last UDS there were some discussions about some of the things people wanted to see in the LoCo Team Portal. Unfortunately it quickly became apparent that while there were plenty of ideas, there is only one active developer, with just a couple others who pitch in with fixes.

In short, we need more developers if we want to see more features and improvements to the directory.

I’ve started taking a look at a couple of bite-size changes, but I’m just learning Django and my time is quite limited. It would be great to have experienced folks pitching in. The other day I worked with Michael Hall (mhall119) and Adnane Belmadiaf (daker) to get the development environment up and running on my 12.04 desktop. During the process daker checked in a change for a bug I ran into and now by using a nice Makefile it’s pretty easy to get going on 12.04.

However, since then, daker has changed the process a bit to make it even easier to get going by shifting to using Vangrant to set up a virtual machine for development.

Instructions for installing on a 64-bit 12.04 Ubuntu system are as follows:

  • Set up bzr on your system, if not already
    • Upload your current ssh key to launchpad.net (if you don’t have one, create one with ssh-keygen)
    • Install bzr: sudo apt-get install bzr
    • bzr whoami “Example User <user@example.com>”
    • bzr launchpad-login username
  • Install vagrant: sudo apt-get install vagrant
  • bzr branch lp:loco-team-portal ltp
  • cd ltp
  • bzr branch lp:ubuntu-django-foundations/bzr-apps loco_directory/bzr_apps
  • bzr branch lp:ubuntu-community-webthemes/light-django-theme loco_directory/ubuntu_website
  • bzr branch lp:twidenash/2.0 loco_directory/media/js/twidenash
  • Download and launch the VM, this will take some time: vagrant up
    • Note: I had some issues here due to a spotty internet connection, if you run into an error you can “vagrant reload” to try again
  • Log in to the vagrant VM: vagrant ssh
  • On the VM you just logged into: cd ltp/loco_directory
  • ./manage.py syncdb
  • ./manage.py migrate
  • ./manage.py runserver

Voila! You now have a LTP instance running on your own system, just open a browser and navigate to

With the sample data loaded up in this install (pulled down from live data a couple weeks ago), for administrative access to the LTP at /admin use the login “admin” and password “123456”

Now for the hard part, fixing bugs and adding features! You’re in luck, as part of the Ubuntu Global Jam this weekend, daker will be hanging out in #ubuntu-website on and off (so be patient!) from 11:00 to 22:00 UTC over the weekend. He can help with whatever questions you may have from installation to tips on how to write Django-focused Python.