~ris/loco-team-portal/fix-552762

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
For the LoCo Team Directory 0.2 we made a couple of changes:

 - modified schema of existing application (just added a key)
 - "rebased" bazaar branch because of megabytes of stuff that were committed unnecessarily
 - Using a loco_settings.py which overides shipped settings.py
 - Now uses LP API unauth'd.

= Preparation =
1. Disable loco-directory service. (a2dissite loco.ubuntu.com (assuming loco.ubuntu.com is the name of the vhost))
2. Backup database.

= Move old stuff away =
1. just in case: bind loco-directory 0.1 to old branch ($ cd /srv/loco.ubuntu.com; bzr pull --remember ~dholbach/loco-directory.0.1)
2. move away: $ mv /srv/loco.ubuntu.com /srv/loco.0.1.ubuntu.com
3. Obtain local changes to settings. ($ cd /srv/loco.0.1.ubuntu.com ; diff -u settings.py.sample settings.py > ~/loco.0.1.settings.diff )

= Re-setup =
1. bzr branch lp:~dholbach/loco-directory/loco-directory.0.2 /srv/loco.ubuntu.com
2. cd /srv/loco.ubuntu.com ; cp local_settings.py.sample local_settings.py
3. populate local_settings.py with changes (refer to ~/loco.0.1.settings.diff for settings to copy).
4. $ ./manage.py syncdb
5. $ ./manage.py migrate teams 0001 --fake
6. $ ./manage.py migrate
7. Update translations, set up jquery symlinks, etc.: $ ./manage.py init

= Enable =
1. Enable loco-directory service (a2ensite loco.ubuntu.com)

= Clean Up - Once loco-directory-dev team are satsified it was successful =
1. $ rm -r /srv/loco.0.1.ubuntu.com