Create API for geojson data in django - django

I know we can use django rest framework for creating API for normal data. But I'm confused can we use django rest framework for geojson data. I'm mean i want to build location based web app using django and I also want to manipulate the data from android app or ios app. So here I'm confused can i use django rest framework or somethings else. Here I'm using PostgreSQL and postgis for data storage.

Related

Django Rest API vs pure Django

I want to build an app that will use a database.
I already build few of them, with models, views, urls... But I discovered that I can build my own API using Django Rest and use this API in my Django project. So if I undersand I will have to separate apps: -an API and my Django app and all my models and database related datas will be in my API app.
If I want to use vue.js for the frontend in my Django app, using an API will make eveything simpler to implement?

How can i use other apps api in my own project?

Let's say i wanted to use the weather api to implement in my django code. I know how to create Rest-api in django but how can i use api of other sources to django itself?

Could the directus app be used in a django stack as a CMS

I am developing a web application in django and react but would like to use directus as a cms. I already have a mysql database and RESTful api set up and working so I was wondering if I could use the directus application as an application within django to manage and update content?
if not what would be the correct way to connect directus to my application? or should I stick with a cms built for integration into django projects?
There is no SDK for django/python yet but you can still use the standard way of HTTP requests instead.
In the docs, you can learn more about how to authenticate and how to make requests or update data.
Docs: https://docs.directus.io/api/reference.html#authentication

Django Post to External Server

I am relatively new to Django/Python. I am currently developing a Django system to track entries to a modelling system our company developed.
Clients should be able to post model run data to a database on our server. The data will be coming from a python script. I was able to make it work on my system using somemodelname.objects.get_or_create, but this will not work externally. I understand I should use a package such as requests and found: How to post a django request to external server. However, this assumes the django code (views, etc) is accessible from the client computer.
How can I make this work so the client data is posted from a python script to the Django database?
Sounds like a good use of a RESTful API. Django Rest Framework and Tastypie are both good packages to use with Django.
Basically, with an API, you can expose your database through urls. You'll have a url like: mysitename.com/api/mymodel that can handle different HTTP methods. If you called that with a POST verb, your view would create a new record for your mymodel model. Thus, when your client computer generates the data in a python script, you would use [requests](http://docs.python-requests.org/en/latest/) to send the data in a POST request to the url endpoint, which would create the record in the database.

Integrate django application with turbogears

I am working with a legacy web application based off of Turbogears 1.1 (CherryPy 2.3) and I would like to integrate it with a Django 1.4 web application. What I would like to do ideally is find some way for both applications to share authentication/session state so that the experience is seamless to the user.
Both applications can run on the same server and technically can access the same mysql database instance.
Initial thoughts are that this could be achieved by:
Storing session data in a shared database
Use the Django application as a 'master' that would issue requests via http to the turbogears application
Running the Django application from within Cherrpy via the internal CherryPyWSGIServer
Any other suggestions would be welcome!
I would suggest looking into creating a custom Django auth and session backend which reuses the existing Turbogears data. You will likely also find it necessary to use Django 1.5's configurable user model.