Something is preventing haystack to listen to the models events, so it is not updating the search index when new instances of TourPoint are create or deleted.

Some endpoints are not documented yet, take a look at it.

The application should run on a Docker container, and be able to run with just a docker-compose up command to facilitate new development environments.

Besides that, it should have vendors applications such as databases and search engines running on isolated containers.

The /api/auth/facebook endpoint is missing tests, it really should be done.

It may be caused by some method overwrite, so it might worth a look.

The API must provide an endpoint to allow users to create new tour points.

The following attributes should be accepted.

• name (string)
• geographical coordinates (float)
• category (string)
• private (boolean)

The category should be restricted to

• Park
• Museum
• Restaurant

There would be nice to have some data to just start digging the api.

The API must allow users to delete a tour point they've created.

If a user is not authenticated she should only see tour points fro the restaurant category

The API must provide an endpoint to allow an user to see all his tour points.

The API must provide an endpoint to allow client apps to request for tour points given a geographical position.

An anonymous user must only see the tour points from restaurant category.

In order to work properly, the application needs an initial index on ElasticSearch.

Should I just add python manage.py rebuild_index on the docker-compose.yml command after generate some fixture data?

Users should be able to signup and sign in using their Facebook accounts.

So the API must provide endpoints to allow client applications request auth tokens for the API by providing a valid facebook user token.

After that, the client app should use the new token provided by the API to authenticate the user on every request from now on.