Package: repopencore
What is it?The intent of this package is to provide a (mostly) automated setup
for running OpenCore on the WSGI-compliant repoze.zope2 stack.This is still experimental; OpenCore isnotguaranteed to run
smoothly in this setup. Please report bugs unique to this setup athttp://trac.openplans.org/openplans/newticket?component=repopencoreThis package is intended to be installed into an existing OpenCore
build. It will not build OpenCore itself. Please readhttp://www.coactivate.org/projects/opencore/getting-startedfor OpenCore installation instructions.How do I use it?Install this package into your OpenCore environment.Generate a configuration file for your deployment:mkopencoreconfig 8080 zope/etc/zope.conf > opencore.iniThe first argument is the port to serve from; this
does not need to be the same port that you serve
your standard OpenCore setup from, and in fact the
two setups can theoretically run in parallel.The second argument is the (absolute or relative) path
to your Zope configuration file, usually found in
{build_dir}/opencore/zope/etc/zope.confStart the server:run-opencore-wsgi zope/bin/zopectl opencore.iniThe first argument is the (absolute or relative) path to
yourzopectlexecutable, usually found in
{build_dir}/opencore/zope/bin/zopectlThe second argument is the path to the configuration file
generated bymkopencoreconfig.Additional arguments like –reload or –daemon can be provided.
They will be passed to thepaster servecommand executed
here; runpaster serve –helpfor available options.If you’re ambitious you should be able to hook this into your
Supervisor setup, buildout configuration, and/or repeatable
Fassembler build. I haven’t tried any of these.What else can it do?There is also an experimental configuration for running a single wsgi
stack with opencore and tasktracker as endpoints, and a Deliverance
middleware set up to theme tasktracker for full visual integration.If you want to try this out, the steps are similar:First, install the extra dependencies with commands provided by
repopencore:install-myghty-fork && install-tasktracker && install-deliveranceThis will install TaskTracker and Deliverance from trunk as well as
a version of Myghty (which is required by a dependency of TaskTracker)
with the following patch applied to myghty.importer at L56:-__builtin__.__import__ = import_module
+#__builtin__.__import__ = import_moduleThat monkeypatch of the built-in __import__ seems to break Zope’s own
munging of sys.path which results in ImportErrors all over the place,
hence the forked installation here.Next, generate a configuration file for your deployment:mkopencoreconfig-with-tt 8080 zope/etc/zope.conf ../../../var/secret.txt  ../../../var/admin.txt ./ > opencore-with-tt.iniThe first two arguments are the same asmkopencoreconfigabove.
The third and fourth arguments are the paths to your shared secret
and admin info files (which are written outside the ./builds directory
by Fassembler, since they don’t change on every build). The last
argument is a base path for TaskTracker to place some of its data
including template caches and the SQLite database.Initialize the TaskTracker database:paster setup-app opencore-with-tt.ini#tasktrackerStart the server:run-opencore-wsgi zope/bin/zopectl opencore.iniCurrently theming (with Deliverance) is not in place, but otherwise the
integration will actually Just Work as long as you’ve configured everything
correctly.It should also be possible to use this configuration with a pre-existing
TaskTracker database; just edit the relevant lines in opencore-with-tt.ini
to point them to your existing database instead of using a newly created
SQLite database.New in this version0.3TaskTracker is now themed with Deliverance. See README.txt for instructions.If you already have anopencore-with-tt.inifile generated from repopencore 0.2,
just add “.deliverance_rule_file = /path/to/repopencore/repopencore/deliverance.xml”
to the[composite:main]section to upgrade.0.2Added support for TaskTracker in WSGI pipeline. See README.txt for instructions.