developmentseed / dustduino-server Goto Github PK

After successful build and deploys to heroku, the app fails and returns Bad Request (400): http://opendustmap.herokuapp.com/api/v1/.

Postgres and Sendgrid seem to be hooked up fine. No obvious errors in logs. When building and running locally is successful and does not return bad request.

@scisco just added you to the opendustmap heroku app as a collaborator. Have any insight into what might be missing here that is causing the error?

@scisco @kamicut are we ok going with re-captcha for this?

Need some way to get sensor location to map in addition to sensor data. Things to think about:

1. where should this be stored?
2. how do users modify?

cc @kamicut

An Admin can create new users, but can't change their passwords. I think the PUT request might not be saving the user password.

@scisco @smit1678

Getting to the point where I can push my work on this API app up here. It currently returns average readings for an arbitrary # of hours. You can also query this data for a specific username, which will correspond to sensors.

Need to do before I push it up here:

• Return one average reading for each hour requested. Currently gives one average reading for all the hours requested.
• Return average reading for all active sensors, or users, for the last hour.

Once I push it up here, the plan is to run the app on the iMac we have in the office and point our own sensors to it so we can start recording actual data. This will work for testing and continuing development.

Endpoint Map

• URL base: /api/v1
  • Sensors: sensors
    • GET sensors lists sensors
    • GET sensors/{sensor_id} lists sensor
    • POST sensors creates a new sensor or if the user exist start the token regeneration process
    • PUT sensorsupdates an existing sensor (will requires email and token)
  • Readings: readings
    • GET readings returns list of latest readings aggregated by hour
    • GET readings/{sensor_id} returns list of readings aggregated for a particular sensor
    • POST readings adds a new reading

In the docs, the URL for the sensor endpoint is listed as:

https://brazil-sensor.herokuapp.com/sensors/sensor_id

Should be:

http://brazil-sensor.herokuapp.com/api/v1/sensors/:sensor_id

We need to document the endpoints that are served by the API, as well as the actions an authenticated user can do on the web browsable interface. Would the documentation be part of the frontend?

Currently, the endpoint is (in optargs notation):

/readings/[aggregate/]?format=json[&users=user1,user2,..][&start_date=yyyy-mm-dd]

• Adding /aggregate/ will aggregate by hour.
• start_date restricts by record creation date after a certain date
• users filters by owner of the record

cc @dereklieu

The custom fields are:

• lat
• lon
• device name
• address
• serial
• email
• description

Also the model should be called sensor

It's probably worth looking into Django REST framework 3.0 before too much work is done here. It's being rolled out now with a lot of improvements and has breaking changes, so probably better to move to it earlier in the process rather than later (if it makes sense to move from 2.4).

http://www.django-rest-framework.org/topics/3.0-announcement/