leylaso / django-etherpad-lite Goto Github PK

Hello,

The README.txt goes into some length to describe how I could share the DATABASE settings inbetween Etherpad and the Django-Etherpad bridge.

I managed to set up my project this way. But do I need to do this? From what I can see, the app mostly uses the API-client, which doesn’t require direct database access? So could I keep the two on separate databases?

Thanks,

Hello,

Trying to run this with Django 1.5 it fails to start the development server with the TypeError: __init__() got an unexpected keyword argument 'verify_exists'. I guess that’s because this functionality is removed from this version:

django.db.models.fields.URLField.verify_exists will be removed. The feature was deprecated in 1.3.1 due to intractable security and performance issues and will follow a slightly accelerated deprecation timeframe.

https://docs.djangoproject.com/en/1.5/internals/deprecation/#id2

The heading says it all. Might get you a patch for this soon.

https://github.com/devjones/PyEtherpadLite

No need to keep writing the curl methods - pull this in as a dependancy and rewrite the model methods to take advantage of it.

Fixed a few issues to make it 1.8 compatible in fork https://github.com/phoebebright/django-etherpad-lite.
Should I do a pull request?

Thinking about using this in an application, any chance I can take a peek at an example deployment to see the capabilities?

Do you have django-etherpad-lite hosted on a webserver somewhere?

I've tried to host it on Heroku and I'm having a really hard time getting it up and running.

You can see here: http://tulsa-etherpad.herokuapp.com

After you create a pad using this app you receive a js error that says,

An error occured while loading the pad
Uncaught Error: The module at "ep_etherpad-lite/static/js/jquery" does not exist. in http://tulsa-etherpad.herokuapp.com/static/js/require-kernel.js (line 569)

Does anyone have any thoughts on this ?

Make sure models are completely covered by tests - including API methods

This means writing our own login view, and adjusting the templates and urls file accordingly