forked from shentonfreude/plone-chris
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.txt
78 lines (49 loc) · 2.07 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
===============================
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.