Revision d49c2fa0 docs/source/devguide.rst
b/docs/source/devguide.rst | ||
---|---|---|
31 | 31 |
========================= ================================ |
32 | 32 |
Revision Description |
33 | 33 |
========================= ================================ |
34 |
0.1 (Jub 24, 2012) Initial release.
|
|
34 |
0.1 (Feb 10, 2012) Initial release.
|
|
35 | 35 |
========================= ================================ |
36 | 36 |
|
37 | 37 |
Overview |
... | ... | |
76 | 76 |
----------------- |
77 | 77 |
|
78 | 78 |
.. image:: images/signup.jpg |
79 |
:scale: 150%
|
|
79 |
:scale: 100%
|
|
80 | 80 |
|
81 | 81 |
Login Flow |
82 | 82 |
---------- |
83 | 83 |
.. image:: images/login.jpg |
84 |
:scale: 150%
|
|
84 |
:scale: 100%
|
|
85 | 85 |
|
86 | 86 |
.. _authentication-label: |
87 | 87 |
|
... | ... | |
104 | 104 |
|
105 | 105 |
User entries can also be modified/added via the administrative interface available at ``/im/admin``. |
106 | 106 |
|
107 |
A superuser account can be created the first time you run the ``manage.py syncdb`` django command. At a later date, the ``manage.py createsuperuser`` command line utility can be used.
|
|
107 |
A superuser account can be created the first time you run the ``manage.py syncdb`` django command and then loading the extra user data from the ``admin_user`` fixture. At a later date, the ``manage.py createsuperuser`` command line utility can be used (as long as the extra user data for Astakos is added with a fixture or by hand).
|
|
108 | 108 |
|
109 | 109 |
Internal Astakos requests are handled using cookie-based django user sessions. |
110 | 110 |
|
... | ... | |
178 | 178 |
400 (Bad Request) The request is invalid |
179 | 179 |
401 (Unauthorized) Missing token or inactive user |
180 | 180 |
500 (Internal Server Error) The request cannot be completed because of an internal error |
181 |
=========================== ===================== |
|
181 |
=========================== ===================== |
Also available in: Unified diff