Permalink
Browse files

reorder site.cfg options

svn path=/plumi.app/trunk/; revision=228617
  • Loading branch information...
1 parent 8265c63 commit 4be3bd9d329565a72d2d302eeba1c2ec5226050c @d-mo d-mo committed Dec 9, 2010
Showing with 49 additions and 31 deletions.
  1. +11 −5 docs/INSTALL.txt
  2. +31 −26 site.cfg
  3. +7 −0 versions/last-production-versions.cfg
View
@@ -9,29 +9,35 @@ Before you start
Install a Plumi 4.x development instance
========================================
-If you simply want to evaluate or develop Plumi, then you don't need a fully fledged production build with caching, multiple load balanced zope instances, etc. A more lightweight buildout is provided. Before runing buildout you may want to customize the options inside site.cfg. Then do the following:
+If you simply want to evaluate Plumi or to contribute in its development, then you don't need a fully fledged production build with caching, multiple load balanced zope instances, etc. A more lightweight buildout is provided. Before runing buildout you may want to customize some of the options inside site.cfg. Then do the following:
python2.6 bootstrap.py -c devel.cfg
./bin/buildout -c devel.cfg
That should take some time. If all goes well your Plumi dev instance will be ready after that point.
-Supervisor should be installed and will be managing the ZEO server and the transcodedaemon. Start supervisor like this:
+Supervisor will be managing the ZEO server and the transcodedaemon. Start supervisor like this:
./bin/supervisord
-To test if zeo and transcodedaemon are up use:
+To see if zeo and transcodedaemon are up use:
./bin/supevisorctl status
-Now start your dev instance
+Now start your dev instance in the foreground
./bin/instance-debug fg
+You should be able to access your instance at http://localhost:8080 unless you changed the default host and port in site.cfg. Login using the credentials in site.cfg (admin:admin by default) and create a new Plone site. Enter a site id ('Plone' by default) and create the site without selecting any setup profiles.
+
Installing Plumi 4.x for production
-===============================
+===================================
+
+This guide assumes that you have sudo access. This is necessary in order to start nginx at port 80, ploneftp at port 21 and for buildout to automatically set the right file permissions for you. Supervisor will be managing all the different services and each service will be limited to the permissions of its effective system user for maximum security. This setup includes all you need in order to run Plumi on a GNU/Linux server for production.
+If you don't have sudo access, you have the option of running all the processes as a single user. Edit site.cfg and set your username in the following fields: supervisor-user, ftp-user, www-user, transcode-user, cache-user, balancer-user, zeo-user and zope-user. Then set the ports in the fields www-address and plumiftp-address to values higher than 1024 (port numbers under 1024 can only be reserved by root)
+
If you want to run plumi and you need caching and multiple load balanced zope instances, a production buildout is provided to make your life easier. Before running buildout, you may want to customize the options inside site.cfg.
python2.6 bootstrap.py -c production.cfg
View
@@ -5,15 +5,37 @@ arch = linux32
# the default Administrator's username and password
user = admin:admin
-# the id of your plumi site
-portal-id = Plone
-
# the address where ZEO will be listening on
zeo-address = localhost:8100
# the address you debug instance will be listening on
instance-debug-address = localhost:8080
+# hostname and port for transcode daemon
+transcode-host = localhost
+transcode-port = 8888
+
+# hostname, port and credentials for supervisor
+supervisor-host = localhost
+supervisor-port = 8890
+supervisor-user = supervu
+supervisor-pass = supervp
+
+# the folder where transcoded videos are being stored
+videofolder = transcoded
+
+# additional eggs that should be available to your portal - leave empty if unsure
+eggs =
+
+# additional zcml includes - leave empty if unsure
+zcml =
+
+
+### The following configuration options are only used by production builds ###
+
+# the id of your plumi site
+portal-id = Plone
+
# the address where Zope's Medusa FTP is listening on
instance-ftp = localhost:8021
@@ -35,22 +57,16 @@ instance2-icp = localhost:8092
instance3-icp = localhost:8093
instance4-icp = localhost:8094
-
-# hostname and port for transcode daemon
-transcode-host = localhost
-transcode-port = 8888
+# effective user for the transcodedaemon process
transcode-user = daemon
+# shared secret for symmetric encryption of transcode requests. If you update it here make sure you also update it in the transcode settings panel.
+secret = 1771d99931264d538e75eeb19da7d6a0
+
# varnish user and address to listen to
cache-user = root
cache-address = localhost:8090
-# hostname, port and credentials for supervisor
-supervisor-host = localhost
-supervisor-port = 8890
-supervisor-user = supervu
-supervisor-pass = supervp
-
# haproxy port and host
balancer-host = localhost
balancer-port = 8089
@@ -65,29 +81,18 @@ www-address = 80
www-server-name = testing.plumi.org
www-videoserver-name = videos.testing.plumi.org
-# zope and zeo will be running as
+# effective user for zope and zeo processes
zeo-user = zope
zope-user = zope
# cache options
zeo-client-cache-size = 1024MB
zodb-cache-size = 10000
-# the folder where transcoded videos are being stored
-videofolder = transcoded
-
-# add here additional eggs that should be available to your portal
-eggs =
-
-# additional zcml includes
-zcml =
-
# the mimetypes supported by default by the transcode profiles below
default_supported_mimetypes = ['application/ogg', 'video/flv', 'video/x-flv', 'video/mpeg', 'video/3gpp', 'video/x-ms-wmv', 'video/ogg', 'video/x-ogg', 'video/x-ogm+ogg', 'video/quicktime', 'video/x-la-asf', 'video/x-ms-asf', 'video/x-msvideo', 'video/mp4']
-# a list of dicts containing the supported transcode profiles {'id':..,'cmd':..,'supported_mime_types':..}
+# a list of dicts containing the supported transcoding profiles {'id':..,'cmd':..,'supported_mime_types':..}
transcode-profiles = [ { 'id' : 'jpeg', 'cmd' : 'scripts/getThumb \"%s\" \"%s\"', 'supported_mime_types': ${site:default_supported_mimetypes}, 'output_mime_type': 'image/jpeg', 'output_extension': 'jpg' }, { 'id' : 'mp4', 'cmd' : 'scripts/transcodeMp4 \"%s\" \"%s\"', 'supported_mime_types': ${site:default_supported_mimetypes}, 'output_mime_type': 'video/mp4', 'output_extension': 'mp4' }, { 'id' : 'ogg', 'cmd' : 'scripts/transcodeTheora \"%s\" \"%s\"', 'supported_mime_types': ${site:default_supported_mimetypes}, 'output_mime_type': 'video/ogg', 'output_extension': 'ogv' }, { 'id' : 'mpeg2', 'cmd' : 'scripts/transcodeMpeg2 %s %s', 'supported_mime_types': ${site:default_supported_mimetypes}, 'output_mime_type': 'video/mpeg', 'output_extension': 'mpg' },{ 'id' : 'dvd', 'cmd' : 'scripts/makeIso %s %s', 'supported_mime_types': 'text/xml', 'output_mime_type': 'application/octet-stream', 'output_extension': 'iso' }, ]
-# shared secret for symmetric encryption of transcode requests. If you update it here make sure you also update it in the transcode settings panel.
-secret = 1771d99931264d538e75eeb19da7d6a0
@@ -2,6 +2,13 @@
PILwoTk = 1.1.6.4
collective.recipe.backup = 1.6
collective.recipe.template = 1.8
+meld3 = 0.6.7
plone.recipe.haproxy = 1.1.1
plone.recipe.varnish = 1.1
scons = 2.0.1
+supervisor = 3.0a9
+z3c.recipe.staticlxml = 0.7.2
+
+#Required by:
+#z3c.recipe.staticlxml 0.7.2
+zc.recipe.cmmi = 1.3.3

0 comments on commit 4be3bd9

Please sign in to comment.