Package: opencore-fassembler_boot
This is a “bootstrap” package that is used to generate new deployments
of the OpenCore software stack, the web-based group collaboration
toolkit that powerscoactivate.organd
other websites.UsageThis package provides two commands for bootstrapping an OpenCore site
installation:new-opencore-sitewill create a directory structure useful for
managing an ongoing OpenCore site deployment.  Run this once, when
you are first deploying your OpenCore site.It will place a fileopencore.confin the generated directory.
You can edit the configuration in this file; it will be used by
therebuild-opencorecommand to determine what profile to
build by default; what portset to configure the stack on; and
other build parameters that are useful to manage on a per-site basis.rebuild-opencore-sitewill initiate a new Fassembler build for your
OpenCore site, using your desired configuration.A third command is provided as well:new-opencore-site-configwill print a site configuration TEMPLATE
to stdout. If you have a site layout already created by OpenplansBoot
this may be useful for quickly generating a configuration that can be
used withrebuild-opencore-site.User / Developer ResourcesThe Opencore Project#opencore <irc://irc.freenode.net/opencore>Changelog0.7.2Pull fassembler-boot from github.com/socialplanning instead of svn.socialplanning.org (sigh)0.7.1Pull fassembler-boot from svn.socialplanning.org instead of svn.openplans.org0.7Theprofile_urlanddefault_profile_urlcan now be specified
as svn://, svn+ssh://, and file:// URLs also.  Previously the only
options were http://, https:// and relative paths (which are treated
as suffixes against https://svn.openplans.org/svn/build/requirements)Update location of default requirement profile to svn.socialplanning.org
instead of svn.openplans.org0.6Prependfile://to etc_svn_repo if no protocol is specified.Fix bug in newbuild.sh script, where it looks for “fassembler-req.txt”,
which was failing when using a relative requirements profile
directory rather than an absolute path.Check that abuildsdirectory exists underbase_dirbefore
running newbuild.sh0.5Add an optional parameter num_extra_zopes which, if set, will
cause N extra zope instances to be installed at the end of the build.Requires fassembler>=0.5 (0.4 which added theextrazopeproject
and 0.5 which added thenum_extra_zopessetting);
opencore-fassembler_projects>=0.3 which now respects thenum_extra_zopessetting when building the frontend; and
libopencore>=0.4 which allows load-balanced proxying to a set of zope
servers.0.4.1Fixed typo in in-process docs.0.4Removed fassembler_projects parameter. Instead, the bootstrap script now looks for
a file “fassembler-req.txt” in the profile directory to be built, since profiles
should manage their own requirements.0.3.2Renamedrebuild-opencore->rebuild-opencore-siteAddednew-opencore-site-configcommand that simply prints the config
template to stdout (useful for existing deployment structures)0.3.1Passing profile_url as a positional arg was broken.  It works now.0.3New package opencore-fassembler_boot, based on OpenplansBoot.Redesigned to use configuration files managed per-site, and to make the newbuild.sh script non-public.0.2Remove –use-plone3 as an option; obsoleted by default-build.ini