Get the publisher test site hosted somewhere

[sean-roberts]

(Description rewritten by @seanh 2017-06-28!)

Problem: We have a publisher test site (simple Flask app, no db) for testing the publisher groups and third-party accounts features for publisher sites that embed the Hypothesis client (e.g. eLife), but getting this site running on your own machine is far too difficult to expect non-developers to do. We'd like the non-developers on the team to have access to an instance of the publisher test site so that they can test and explore the publisher features.

Solution: Get an instance of the publisher test site hosted somewhere, for example on our own AWS infrastructure, or on Heroku.

Details:

• The instance should use the production https://hypothes.is/ web service and the production CDN-hosted Hypothesis client.
• An authority, authclient, publisher group, etc for the test site instance will need to be created in the production database, as we've done for eLife
• A correctly configured instance of the publisher test site will need to be hosted somewhere <- We've decided to try Heroku using the Hypothesis Heroku team account

Issues:

• The publisher test site has no security. You just click the login button, type in any user name you want and no password, and it creates the user account for you in the production https://hypothes.is/ database (under its own authority's namespace). Is this an issue or are we happy to allow this? <- I think we are happy allow this, see Slack discussion

[sean-roberts]

At a high level this will require:

• adding a staged "integrator"
• hosting the publisher demo project (python based)

[robertknight]

We have a shared Heroku account now which I believe we could use to host the publisher demo site, a simple Flask-based app with no database.

[seanh]

I've edited the issue description above with more details