plone/heroku-button-plone

A template for a simple Heroku-hosted Plone site.

heroku-button-plone's Issues

Make the Heroku Button app an importable egg + prepare z3c.jbot

So, the Heroku Button is just a template. Making it an egg, we can import it in "heroku.cfg" and then we can have a pre-made z3c.jbot directory and then we can tell users: if you need to override a template, just throw it in the "overrides" directory, and push changes to Heroku. Profit.

CI for Heroku Button

Hook into Travis and run buildout on every commit to check we don't break anything.

Demo content

How can we install demo content in Heroku Button Plone instances?

The problem is that when buildout is run, we do not yet have access to postgres (access is configured in configure_zope_conf.py that is run just before we start the instance) so that we cannot create demo content with collective.recipe.democontent.

Can we create demo content on instance start? Alternatively, can we get access to postgres while running buildout (so in the bin/compile step in the buildpack)?

The addon "pgbackups" does not exist

Hi guys

cc @zupo

When I try to deploy a heroku button for plone shows the following message:

There was a problem with the app.json file found at "https://github.com/plone/heroku-button-plone":
The addon "pgbackups" does not exist. Please ensure that the addon is spelled correctly.

Add local.cfg

Add local.cfg and explain how to build user's instance of the Heroku Button app locally and how to run it locally (so they can test things out).