Plone plumi install

Blog Archive. Plumi now on Debian Jessie, Ubuntu Plumi is now available to install on Debian Jessie, Ubuntu Subscribe to the EngageMedia mailing list. Two emails a month of all our best posts. View past newsletters. Mastodon Twitter Rss. Updates Blog Newsletter Podcast Resources. Contact Donate Privacy Policy. Production buildout sets up and configures an nginx web server based on your site.

However, if your server already has Apache set up on it eg: for hosting other, non-Plumi sites , you can stop nginx and use configure apache to use with plumi.

Here is the apache configuration for demo. If you've used a non-standard port for Zope, replace the in the URL above with the port you have specified when configuring the buildout. NOTE: Replace the "zope" in "su zope -c" with the name of the user you installed Plumi under the "effective-user" from site. If you are having trouble installing Plumi please join one of our email lists or IRC channels listed here or contact the Plumi maintainers here.

You may encounter difficulties if you are already running a Plumi site from another buildout on this webserver note that you would usually add another Plone site within the one buildout rather than run multiple sites from different buildouts. You will also need to change the default ports in the installation's site. However, even in those cases you may wish to customize some of the options inside site. If you're deploying for production you should have 2 different hostnames available, one for your Plumi site e.

You could also install the transcoding server in a different machine or even have multiple transcoding servers with load balancing, but this setup will not be covered in this guide. Please ensure that these hostnames are set up in advance of your site installation and have had sufficient time to propagate through the Internet eg: hours. Before running buildout, you should customize the options inside site. At the very least you should change the following:. If you decided not to change the default user for zope, zeo and transcode in site.

If not, add it:. Once you're ready with the initial configuration execute the following two commands. That should take some time, so feel free to get some cofee or fresh air while buildout is downloading, compiling and installing dependencies Zope, Plone, ffmpeg, etc.

If all goes well your Plumi instance will be ready after that point. Supervisor will be managing the internal ZEO server, the transcodedaemon, the async worker instance, the varnish cache server, the uwsgi WSGI web server, as well as the externally facing ploneFTP server and the nginx web server in production builds. Beta 2 includes lot of changes, including the use of collective.

Includes migration code to move from Plumi 0. Previous Plumi 0. Jan 30, Nov 18, Jul 26, Jul 16, Apr 11, Jan 5, Dec 21, Dec 18, Jul 2, Jun 8, Jun 3,