@@ -18,28 +18,43 @@ General Instructions for Deployment of a New Release
1818
1919 cp $oldreleasenumber/ietf/settings_local.py $releasenumber/ietf/
2020
21- 3. Change into the directory of the new release and run migrations::
21+ 3. Change into the directory of the new release: and run migrations::
2222
2323 cd $releasenumber
24- PYTHONPATH=$PWD ietf/manage.py migrate
25- cd ..
2624
27- 4. Then re-point the 'web' symlink::
2825
26+ 3.5 Optionally, set up a Python virtual environment:
27+
28+ virtualenv .
29+ source bin/activate
30+
31+ 4. Install requirements (make sure your pip is reasonably fresh first).
32+ The following will install required python modules locally if you
33+ are using a virtualenv, or globally if you are not:
34+
35+ pip install -r requirements.txt
36+
37+ 5. Run migrations:
38+
39+ ietf/manage.py migrate
40+
41+ 6. Back out one directory level, then re-point the 'web' symlink::
42+
43+ cd ..
2944 rm ./web; ln -s $releasenumber web
3045
31- 5 . Restart apache::
46+ 7 . Restart apache::
3247
3348 sudo /etc/init.d/apache2 restart
3449
35- 6 . It's now also a good idea to go to the datatracker front page:
50+ 8 . It's now also a good idea to go to the datatracker front page:
3651
3752 http://datatracker.ietf.org/
3853
3954 to check that it's alive and kicking, and displaying the new release
4055 number at the bottom of the left-side menubar :-)
4156
42- 7 . If things **aren't** cool, revert the symlink step, re-pointing the
57+ 9 . If things **aren't** cool, revert the symlink step, re-pointing the
4358 symlink to the release that was running before the new release, and restart
4459 apache again to roll back to that.
4560
0 commit comments