Skip to main content
Join the official 2020 Python Developers SurveyStart the survey!

Creates a setup for new OpenCore site deployments that use Fassembler

Project description

This is a “bootstrap” package that is used to generate new deployments of the OpenCore software stack, the web-based group collaboration toolkit that powers and other websites.


This package provides two commands for bootstrapping an OpenCore site installation:

  • new-opencore-site will 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 file opencore.conf in the generated directory. You can edit the configuration in this file; it will be used by the rebuild-opencore command 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-site will initiate a new Fassembler build for your OpenCore site, using your desired configuration.

A third command is provided as well:

  • new-opencore-site-config will 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 with rebuild-opencore-site.

User / Developer Resources



Pull fassembler-boot from instead of (sigh)


Pull fassembler-boot from instead of


The profile_url and default_profile_url can 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

Update location of default requirement profile to instead of


Prepend file:// to etc_svn_repo if no protocol is specified.

Fix bug in 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 a builds directory exists under base_dir before running


Add 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 the extrazope project and 0.5 which added the num_extra_zopes setting); opencore-fassembler_projects>=0.3 which now respects the num_extra_zopes setting when building the frontend; and libopencore>=0.4 which allows load-balanced proxying to a set of zope servers.


Fixed typo in in-process docs.


Removed 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.


Renamed rebuild-opencore -> rebuild-opencore-site

Added new-opencore-site-config command that simply prints the config template to stdout (useful for existing deployment structures)


Passing profile_url as a positional arg was broken. It works now.


New package opencore-fassembler_boot, based on OpenplansBoot.

Redesigned to use configuration files managed per-site, and to make the script non-public.


  • Remove –use-plone3 as an option; obsoleted by default-build.ini

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Files for opencore-fassembler_boot, version 0.7.2
Filename, size File type Python version Upload date Hashes
Filename, size opencore-fassembler_boot-0.7.2.tar.gz (7.1 kB) File type Source Python version None Upload date Hashes View

Supported by

Pingdom Pingdom Monitoring Google Google Object Storage and Download Analytics Sentry Sentry Error logging AWS AWS Cloud computing DataDog DataDog Monitoring Fastly Fastly CDN DigiCert DigiCert EV certificate StatusPage StatusPage Status page