Changes between Version 6 and Version 7 of WikiStart
- Timestamp:
- 01/08/10 12:23:56 (8 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v6 v7 6 6 7 7 If you've already got a "master" database and want to start tracking its changes, import your production copy as trunk@HEAD, then tag it as tags/master-1.0 (or whatever version number you choose to start with). Developers can then checkout trunk@HEAD, make changes for new features or to fix bugs in their local working copy, then commit their changes to trunk. They can also make branches as needed for collaboration or QA, and merge those changes back into trunk once approved. When everything is ready, upgrade your production server to trunk@HEAD (or a new tag as you see fit). 8 9 So: 10 11 {{{ 12 $ pf import -U postgres --force <dbname> postfacto://me@server/repodb/myproject/trunk 13 Committed revision 1. 14 15 $ pf add -U postgres pmx_test "*" 16 Added 556 objects: 17 constraints: cache.jobs, cache.runs, public.accounts, 18 <lots more lines> 19 20 $ pf commit -m "Existing schema." <dbname> 21 Committed revision 2. 22 }}} 8 23 9 24 Read [http://www.post-facto.org/chrome/common/doc/ the documentation] for the most-recent version (once it's uploaded!). … … 15 30 You can also find source and binary distributions (once we release something ;) at http://www.post-facto.org/chrome/common/releases/. 16 31 32 {{{ 33 $ svn co http://svn.post-facto.org/postfacto/trunk/ 34 ... 35 Checked out revision 34. 36 $ cd trunk 37 $ python setup.py install 38 ... 39 copying build/scripts-2.5/pf.py -> /home/fumanchu/envs/pf/bin changing mode of /home/fumanchu/envs/pf/bin/pf.py to 755 ... 40 }}} 41 42 Then, make a symlink from /usr/bin/pf to your new "pf.py" file (you can see where mine got copied to above; yours will differ). `pf` should then give you help output: 43 44 {{{ 45 $ pf 46 Usage: pf [options] command *args 47 48 Options: 49 -h, --help show this help message and exit 50 ... 51 }}} 52 17 53 = Community and Contact = 18 54
