Building everything from source on Linux, for a production site
---------------------------------------------------------------

You can now use a buildout -- check http://plumi.org/browser/plumi-buildout-plone2.5

** 
The steps below are show old versions of plone, as of 12th Dec 2007 
please consider using the latest plone version at the time of your install.
(12th Dec 2007 , thats plone 2.5.5 )
**

$ cd ; mkdir plumibuild ; cd plumibuild
$ wget http://www.zope.org/Products/Zope/2.9.8/Zope-2.9.8-final.tgz
$ wget http://plone.googlecode.com/files/Plone-2.5.3-final.tar.gz
$ svn co https://svn.plone.org/svn/collective/Plumi/trunk Plumi
$ tar zxvf Zope-2.9.8-final.tgz
$ tar zxvf Plone-2.5.3-final.tar.gz
$ cd Zope-2.9.8-final
$ sudo ./configure --prefix=/opt/Zope-2.9.8
$ sudo make 
$ sudo make install
$ sudo /opt/Zope-2.9.8/bin/mkzopeinstance.py

# we have a installed Zope instance at this stage installed in /path/to/instance
# we should update zope.conf to specify:
# the http port to run zope on, a line for Plone products and a line for Plumi products
#eg # products /path/to/Plone-2.5.3
#   # products /path/to/Plumi
# effective-user zope
# you can also use security-policy-implementation python and verbose-security on
#during debugging.


# now, start Zope, install a Plone site via ZMI
# then add Plumi products (ATVideo and PlumiSkin are sufficient)
 
$ cd /path/to/instance
$ sudo ./bin/zopectl start

New versions of locally produced Products, and Plumi itself
-----------------------------------------------------------
1. Build everything from the trunk, rather than tagged versions, esp ATVideo/branch/engage
and PlumiSkin/trunk
	do this by making local modification to EXTERNALS.txt to point listed Products to trunk versions rather than tag versions for instance
	reapply the EXTERNALS.txt file locally (do not check it in!)
	eg svn propset svn:externals -F EXTERNALS.txt .
	do svn update to get the trunk versions , and away you go

2.Once you have ironed out bugs/introduced new features etc, you can tag from there.
(eg 
$ svn copy https://svn.plone.org/svn/collective/PlumiSkin/trunk https://svn.plone.org/svn/collective/PlumiSkin/tags/engagemedia-plumi-0.6
)

3. Update and test on a separate Plumi testing box, deployed using Plumi/trunk, then you can tag a new release of Plumi itself.


Bug Tracker
-----------
See the bug tracker http://plumi.org/report/3

Making Contact
--------------
see Making Contact in the README.txt, for places to ask questions

Customisations we have made to various Plone Products
-----------------------------------------------------


qRSS2Syndication - templates we have overridden:
	see ATVideo/skins/ATEngageVideo/setup_rss2.cpt save_rss2_setup.cpy
	ATVideo/skins/ATEngageVideo/RSS2.pt atengagevideo_item.pt

ContentLicensing - we have made custom widget for embedding this in the edit form
	see ATVideo/skins/ATEngageVideo/atvideo_widgets/contentlicensing_widget.pt
	ATVideo/Widgets.py

ATVocabularyManager - see the monkeypatch in ATVideo/__init__.py
