django-rest-framework/docs/tutorial/quickstart.md

139 lines
4.8 KiB
Markdown
Raw Normal View History

2012-10-09 15:01:17 +04:00
# Quickstart
We're going to create a simple API to allow admin users to view and edit the users and groups in the system.
Create a new Django project, and start a new app called `quickstart`. Once you've set up a database and got everything synced and ready to go open up the app's directory and we'll get coding...
## Serializers
First up we're going to define some serializers in `quickstart/serializers.py` that we'll use for our data representations.
2013-05-02 15:08:05 +04:00
from django.contrib.auth.models import User, Group
2012-10-09 15:01:17 +04:00
from rest_framework import serializers
class UserSerializer(serializers.HyperlinkedModelSerializer):
class Meta:
model = User
fields = ('url', 'username', 'email', 'groups')
class GroupSerializer(serializers.HyperlinkedModelSerializer):
class Meta:
model = Group
2013-05-02 15:08:05 +04:00
fields = ('url', 'name')
2012-10-09 15:01:17 +04:00
Notice that we're using hyperlinked relations in this case, with `HyperlinkedModelSerializer`. You can also use primary key and various other relationships, but hyperlinking is good RESTful design.
## Views
2012-10-12 12:02:21 +04:00
Right, we'd better write some views then. Open `quickstart/views.py` and get typing.
2012-10-09 15:01:17 +04:00
from django.contrib.auth.models import User, Group
2013-05-02 15:08:05 +04:00
from rest_framework import viewsets
2012-10-09 15:01:17 +04:00
from quickstart.serializers import UserSerializer, GroupSerializer
2013-05-02 15:08:05 +04:00
class UserViewSet(viewsets.ModelViewSet):
2012-10-09 15:01:17 +04:00
"""
2013-05-02 15:08:05 +04:00
API endpoint that allows users to be viewed or edited.
2012-10-09 15:01:17 +04:00
"""
2013-05-02 15:08:05 +04:00
queryset = User.objects.all()
2012-10-09 15:01:17 +04:00
serializer_class = UserSerializer
2013-05-02 15:08:05 +04:00
class GroupViewSet(viewsets.ModelViewSet):
2012-10-09 15:01:17 +04:00
"""
2013-05-02 15:08:05 +04:00
API endpoint that allows groups to be viewed or edited.
2012-10-09 15:01:17 +04:00
"""
2013-05-02 15:08:05 +04:00
queryset = Group.objects.all()
2012-10-09 15:01:17 +04:00
serializer_class = GroupSerializer
2013-05-02 15:08:05 +04:00
Rather that write multiple views we're grouping together all the common behavior into classes called `ViewSets`.
We can easily break these down into individual views if we need to, but using viewsets keeps the view logic nicely organized as well as being very concise.
2012-10-09 15:01:17 +04:00
## URLs
2013-05-02 15:08:05 +04:00
Okay, now let's wire up the API URLs. On to `quickstart/urls.py`...
2012-10-09 15:01:17 +04:00
from django.conf.urls import patterns, url, include
2013-05-02 15:08:05 +04:00
from rest_framework import routers
from quickstart import views
2012-10-09 15:01:17 +04:00
2013-05-02 15:08:05 +04:00
router = routers.DefaultRouter()
router.register(r'users', views.UserViewSet)
router.register(r'groups', views.GroupViewSet)
2012-10-09 15:01:17 +04:00
2013-05-02 15:08:05 +04:00
# Wire up our API using automatic URL routing.
# Additionally, we include login URLs for the browseable API.
urlpatterns = patterns('',
url(r'^', include(router.urls)),
2012-10-09 15:01:17 +04:00
url(r'^api-auth/', include('rest_framework.urls', namespace='rest_framework'))
)
2013-05-02 15:08:05 +04:00
Because we're using viewsets instead of views, we can automatically generate the URL conf for our API, by simply registering the viewsets with a router class.
2012-10-09 15:01:17 +04:00
2013-05-02 15:08:05 +04:00
Again, if we need more control over the API URLs we can simply drop down to using regular class based views, and writing the URL conf explicitly.
2012-10-09 15:01:17 +04:00
2013-05-05 21:12:35 +04:00
<<<<<<< HEAD
2013-05-02 15:08:05 +04:00
Note that we're also including default login and logout views for use with the browsable API. That's optional, but useful if your API requires authentication and you want to use the browseable API.
2013-05-05 21:12:35 +04:00
=======
Finally, we're including default login and logout views for use with the browsable API. That's optional, but useful if your API requires authentication and you want to use the browsable API.
2013-05-05 21:12:35 +04:00
>>>>>>> master
2012-10-09 15:01:17 +04:00
## Settings
We'd also like to set a few global settings. We'd like to turn on pagination, and we want our API to only be accessible to admin users.
INSTALLED_APPS = (
...
'rest_framework',
)
REST_FRAMEWORK = {
'DEFAULT_PERMISSION_CLASSES': ('rest_framework.permissions.IsAdminUser',),
2012-10-09 15:01:17 +04:00
'PAGINATE_BY': 10
}
2012-12-05 15:20:03 +04:00
Okay, we're done.
---
## Testing our API
We can now access our API, both from the command-line, using tools like `curl`...
bash: curl -H 'Accept: application/json; indent=4' -u admin:password http://127.0.0.1:8000/users/
{
"count": 2,
"next": null,
"previous": null,
"results": [
{
"email": "admin@example.com",
"groups": [],
"url": "http://127.0.0.1:8000/users/1/",
"username": "admin"
},
{
"email": "tom@example.com",
"groups": [ ],
"url": "http://127.0.0.1:8000/users/2/",
"username": "tom"
}
]
}
Or directly through the browser...
![Quick start image][image]
Great, that was easy!
If you want to get a more in depth understanding of how REST framework fits together head on over to [the tutorial][tutorial], or start browsing the [API guide][guide].
2012-10-09 17:12:38 +04:00
[image]: ../img/quickstart.png
[tutorial]: 1-serialization.md
[guide]: ../#api-guide