On 03/12/15 06:51, Lisha Sterling wrote:
> Trying to install a local copy of waterpoints on a new laptop, but it
> won't even start. I'm guessing this may have to do with the same Eve 6.0
> problem.
The same? Same as what?
> ___
> (TaarifaAPI)lishevita@Monotropa-uniflora ~/Code/TaarifaAPI $ python
> taarifa_api/taarifa_api.py
> Traceback (most recent call last):
> File "taarifa_api/taarifa_api.py", line 3, in <module>
> from eve import Eve
> File
> "/home/lishevita/.virtualenvs/TaarifaAPI/local/lib/python2.7/site-packages/Eve-0.6-py2.7.egg/eve/__init__.py",
> line 87, in <module>
> from eve.flaskapp import Eve # noqa
> File
> "/home/lishevita/.virtualenvs/TaarifaAPI/local/lib/python2.7/site-packages/Eve-0.6-py2.7.egg/eve/flaskapp.py",
> line 17, in <module>
> from events import Events
> ImportError: No module named events
> ____
>
> So, which versions of Eve and Mongo do work? Are you able to run a local
> version with current code from github and those downgraded versions? Or
> do you see some other obvious problem here that I've failed to notice?
I don't understand what you mean by downgraded versions?
TaarifaAPI definitely works with Eve 0.6 (in fact that is now required).
How did you install the dependencies? Running `pip install -r
requirements.txt` in your virtualenv should get you correct versions.
> We have an end use feedback opportunity today with COWSOs and the
> district water engineer in Bunda town. The intent here is to use
> TaarifaWaterpoints as the base for the web-based ticketing and reporting
> system while SEMA works as the report intake tool. In order to build the
> right user interface, though, we need information from the stakeholders
> that would actually be using that web front end (as opposed to the USSD
> tool used by field reporters which is from SEMA).
Sorry, but if you'd like us to help out we need much more notice than
this. I work full time and it's only by chance I have a few mins this
morning before heading off to work.
> I don't even so much as have screenshots of the different kinds of
> reports, so getting feedback is going to be impossible unless I can get
> a local version TaarifaWaterpoints working.
Indeed. Dirk already pointed you to the relevant gh issue #187, where I
describe the problem: Heroku now enforces a 30s limit on any request and
we're failing that for *all* the XHR requests we're serving on the
dashboard. You can confirm that by watching the network tab in the
Chrome dev tools (filter for XHR requests).
There's no quick fix for this. It will require a complete redesign of
the dashboard architecture and neither Dirk nor I have the capacity to
work on this in our spare time.
> Thank you for your eyes and ideas!
I don't think anybody else will be able to jump in to help you with this
on such short notice.
Best of luck!
Florian