Development

Differences between revisions 14 and 15
Revision 14 as of 2011-11-12 02:06:42
Size: 2373
Editor: ip72-196-101-83
Comment:
Revision 15 as of 2011-11-17 02:48:43
Size: 2944
Editor: ip72-196-101-83
Comment:
Deletions are marked like this. Additions are marked like this.
Line 49: Line 49:
= Django Commands and Install Commands =

== Sync Database(different from the make commands) ==
 ''cd /rootProjectDirectory''

 ''cd /loco-team-portal''

 ''../env/bin/python manage.py syncdb''

== OpenID Sync ==
This may take a while, a very long while. As the IRC channel has said, start this command and then
 * go take a walk
 * get a cup of coffee or tea
 * read war and peace
 * have a Lord of the Rings extended edition marathon

 ''cd /rootProjectDirectory''

 ''cd /loco-team-portal''

 ''../env/bin/python manage.py update-openids''

Please share your favourite tips and tricks here.

Release

  • our release process

  • if a fix gets merged,
    • mark bug as 'fix committed'
    • assign to whoever fixed it
    • milestone to current milestone

Database

  • You can download this db loco_directory.db, the django admin logins:

    • Login: daker
    • Passe: ltp

Schema changes

  • if a fix needs changes to the database models, please use the bug tag schema-change

  • when writing migration scripts, make sure you use python-django-south 0.6, if necessary set up a lucid chroot (DebootstrapChroot)

  • to test migrations, test them back and forth:

    ./manage.py migrate <app>; ./manage.py migrate <app> zero
  • because we set the database table name in the teams models (we shouldn't have done that, but it's too late to fix it), you might have to use the following runes in migrations scripts to make them work:

    db.current_orm.models['teams'] = db.current_orm.models['teams.team']

How to fix a bug ?

Here are the steps to follow :

  • Get a copy of the main branch :
    • $ bzr branch lp:loco-team-portal fix.<bug_id>

  • Make your changes to fix that bug.
  • Once you've done, run the following commands :
    • $ bzr add
    • $ bzr commit --fixes lp:<bug_id> , then write what you have done on the text-editor.

    • $ bzr push lp:~<you-lp-id>/loco-team-portal/fix.<bug_id>

    • $ bzr launchpad-open
    • Once the browser window appears, click on "Propose for merging" and wait for someone from the LD devs to review it.

Using Virtualenv

Virtualenv will let you setup a working environment for loco-team-portal that will not conflict with your system-wide environment. This is the best way to work on LD locally if you're running something other than Ubuntu 10.04 (Lucid).

  1. sudo apt-get install python-virtualenv
  2. cd {branch root}
  3. virtualenv --python=/usr/bin/python2.6 .env
  4. source .env/bin/activate
  5. pip install -r requirements.txt

Hint: Run "deactivate" to leave the virtualenv

= Django Commands and Install Commands =

Sync Database(different from the make commands)

  • cd /rootProjectDirectory

    cd /loco-team-portal

    ../env/bin/python manage.py syncdb

OpenID Sync

This may take a while, a very long while. As the IRC channel has said, start this command and then

  • go take a walk
  • get a cup of coffee or tea
  • read war and peace
  • have a Lord of the Rings extended edition marathon

    cd /rootProjectDirectory

    cd /loco-team-portal

    ../env/bin/python manage.py update-openids


CategoryLoco

LoCoTeamPortal/Development (last edited 2011-11-17 02:48:43 by ip72-196-101-83)