Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Personal Plone site buildout
Python

This branch is 4 commits ahead, 7 commits behind shentonfreude:master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
docs
download-cache
.gitignore
README.txt
addon-versions.cfg
base.cfg
bootstrap.py
buildout.cfg
production.cfg
theming-versions.cfg

README.txt

===============================
 README: Installing this Plone
===============================

Create Non-tracked Passwords file
=================================

Create a file `passwords.cfg` that is *not* tracked in the repo, and
place your plone's admin username and password in it like::

  [passwords]
  instance_user = admin:MySecretPassword

Virtualenv
==========

Create and activate a virtual environment. I'm using Python-2.7 as
it's Plone now works well with it::

  /usr/local/python/2.7/bin/virtualenv --no-site-packages --distibute .
  source bin/activate

Build
=====

Bootstrap the buildout::

  bin/python bootstrap.py

Build it and tell it not to check for versions it already has::

  bin/buildout -N

If you're using the production config, it should ask for your sudo
password at the end to fix permissions such that a 'plone' user owns
various files in var/.

Test
====

Test them out; for development we don't need sudo::

  bin/zeoserver start
  bin/instance1 fg

Login as 'admin' and the password you set in 'passwords.cfg' to the
site on localhost with your instance's port from buildout.cfg and see
if it tells you that you need to upgrade. Then Site Setup and then the
Zope Management Interface for items needing upgrades.

Run for Production
==================

This buildout uses `supervisor` to run the daemons and will restart them if memory grows too large.  The supervisord should be started at boot time with an init.d/ type of script, something like::

	${instancedir}/bin/supervisord

You can check on it with::

	${instancedir}/bin/supervisorctl status

And shut down everything with::

	${instancedir}/bin/supervisorctl shutdown


Packing the Database
====================

If you're remote, you may have to access the top-level admin area by
tunneling to the port since an Apache rewrite will likely prevent you
reaching this high up; replace 60001 with your instance's port::

  ssh -L 60001:localhost:60001 serverhostname

then connect to http://localhost:60001

From there go to the Zope Management Interface, Contrl Panel, Database Management, main to pack the database.
Something went wrong with that request. Please try again.