Permalink
Browse files

Prepare plumi.app 4.2rc2.

svn path=/plumi.app/trunk/; revision=239551
  • Loading branch information...
1 parent 50bf3c6 commit 0c07b5a38872444f843cc7179eeb5467a5094e14 @d-mo d-mo committed May 19, 2011
Showing with 55 additions and 28 deletions.
  1. +32 −0 docs/CHANGES.txt
  2. +21 −26 docs/INSTALL.txt
  3. +1 −1 production.cfg
  4. +1 −1 site.cfg
View
@@ -1,8 +1,40 @@
+4.2rc2 (2011-05-19) [unweb.me]
+==============================
+
+ - install base plumi profiles on site creation [clopy]
+ - restore default effective user name to zope [clopy]
+ - fix permission issues on production buildout [clopy, dimo]
+ - configure PYTHON_EGG_CACHE [dimo]
+ - update navtree-patch [clopy]
+ - disable Werror compile option to prevent possible nginx breakage [dimo, clopy]
+ - unpin plumi.app since we should already have it [dimo]
+ - use 3 threads and 3 maxconnections per instance in production buildouts [dimo]
+ - automatically create plumi site on first buildout run [dimo]
+ - update to Plone 4.0.5 & add collective.xdv in buildout [dimo]
+ - move plumi egg pins to production buildout only, dev buildout should work with latest trunks [dimo]
+ - ftp-user should be root by default in order to bind to port 21 [dimo]
+ - remove effective user from zeoserver buildout section, since supervisor takes care of that, prevents possible permission issue in dev buildouts [dimo]
+ - update INSTALL docs [dimo]
+ - get thumb from 8th second instead of 4th [dimo]
+ - force lxml build to prevent possible ngnix build issue if lxml already present [dimo]
+ - do not use content language negotiation by default [clopy]
+
+
+4.2rc1 (2011-05-10) [unweb.me]
+==============================
+
+ - enable 2 instances by default in production builds [dimo]
+ - change default user mappings and varnish port [dimo]
+ - use setuptools by default instead of distribute in bootstrap.py [dimo]
+ - update plumi manual link [dimo]
+
+
4.1.2 (2011-03-26) [unweb.me]
=============================
- updated navtree patch for plone 4.0.4 [clopy]
+
4.1.1 (2011-03-09) [unweb.me]
=============================
View
@@ -13,7 +13,8 @@ Before you start
e.g. sudo apt-get install python2.6-dev
* install libjpeg and zlib header files
e.g. sudo apt-get install libjpeg62-dev zlib1g-dev
- or for Ubuntu 11.04: sudo apt-get install libjpeg8-dev
+ or for Ubuntu 11.04 jpeg support: sudo apt-get install libjpeg8-dev
+ for png support in Ubuntu 11.04 you may have to install zlib from source
* install groff-base
e.g. sudo apt-get install groff-base
* install libxslt header files
@@ -51,21 +52,14 @@ 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. Create a new Plone site using
-the credentials in site.cfg (admin:admin by default, to change them after the
-initial setup go to http://localhost:8080/acl_users/users/manage_users ).
-Enter a site id ('Plone' by default) and create the site without selecting any
-add-ons at this point.
-
-Once your Plone site has been created, go to the Add-ons configuration section
-(e.g. http://localhost:8080/Plone/prefs_install_products_form ) and install the
-Plumi 4.x add-on.
+You should be able to access your Plumi instance at http://localhost:8080/Plone
+unless you changed the default host, port or site-id in site.cfg. You can login
+as an admin using the credentials in site.cfg (admin:admin by default).
If you have changed the default port, hostname, or the secret encryption key
-for transcode daemon in site.cfg, go to the transcode settings panel
-(e.g. http://localhost:8080/Plone/@@transcode-controlpanel ) and enter the same
-host, port and key there.
+for the transcode daemon in site.cfg, you should go to the transcode settings
+panel (e.g. http://localhost:8080/Plone/@@transcode-controlpanel ) and enter
+the same host, port and key there.
Your dev instance should be ready for testing at this point. Add a new user to
your Plumi site for testing (the admin user may not have the correct folders
@@ -155,30 +149,31 @@ Confirm that all the services have been started:
./bin/supervisorctl status
+You should now be able to view your site at the hostname you configured in
+site.cfg (www-server-name setting e.g. http://testing.plumi.org) as long as
+the hostname is configured correctly and points to the ip address of your
+server. Also verify that you can access the transcode daemon and videoserver
+in the hostname you provided in site.cfg (www-videoserver-name e.g
+http://videos.testing.plumi.org).
+
A debug instance is also created during the production buildout but not started
by default. If you need to test, debug and catch errors on your production
environment you can start it in the foreground:
./bin/instance-debug fg
-You should be able to access your instance through the load balancer at
-http://localhost:8089 unless you changed the default balancer host and port in
-site.cfg. Create a new Plone site using the credentials in site.cfg. Enter a
-the site-id you defined in site.cfg ('Plone' by default) and create the site
-without selecting any add-ons at this point.
+By default the debug instance will listen on any ip address provided by your
+server, on port 8080 (instance-debug-address in site.cfg)
-Once your Plone site has been created, go to the Add-ons configuration section
-(e.g. http://localhost:8089/Plone/prefs_install_products_form ) and install the Plumi 4.x add-on.
+You can login to your new Plumi site using the admin credentials you provided
+in site.cfg (admin:admin by default).
-Now go to the transcode settings panel (e.g.
-http://localhost:8089/Plone/@@transcode-controlpanel ) and enter the
+Once you login for the first time, go to the transcode settings panel (e.g.
+http://testing.plumi.org/@@transcode-controlpanel ) and enter the
www-videoserver-name set in site.cfg and the updated secret key. You may also
want to configure caching by installing the http caching support in the add-ons
configuration section.
-From this point, you should be able to access your site through nginx at the
-url that you configured in site.cfg (www-server-name).
-
Add a new user to your Plumi site for testing (the admin user may not have the
correct folders created, as this user is created before the Plumi site is
generated). Log out and log back in as your new user.
View
@@ -22,7 +22,7 @@ develop = src/collective.contentlicensing
.
[versions]
-plumi.content = 4.2rc1
+plumi.content = 4.2rc2
plumi.skin = 4.2rc1
plumi.locales = 4.2
collective.piwik.flowplayer = 0.4
View
@@ -117,7 +117,7 @@ zeo-client-cache-size = 1024MB
zodb-cache-size-bytes = 102400000
# 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']
+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', 'video/mkv']
# 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' }, { 'id' : 'low', 'cmd' : 'scripts/transcodelow \"%s\" \"%s\"', 'supported_mime_types': ${site:default_supported_mimetypes}, 'output_mime_type': 'video/mp4', 'output_extension': 'mp4' }, ]

0 comments on commit 0c07b5a

Please sign in to comment.