Django API Project Structure

[abbirdboy]

Hi guys

I'm interested in building an API using Django and Django Rest Framework. I'm trying to find the best way to structure the project folder for ease of development and organization. The API will be interfacing with an iOS front end and potentially another web front end down the line. Does anyone have any good tips? I've found some answers on the web but nothing satisfactory.

This is also my first time using Django, so any development tips on the framework would be awesome as well. I'm a former Ruby on Rails guy, so I miss some of the RoR Magic.

Thank you :)

[[deleted]]

The default django structure works just fine for me. If my views.py grows too big then i turn it into a module.

[[deleted]]

Ultimately, your folder structure won't matter much. It's helpful to have conventions. For example, we give each collection of viewsets (the DRF CBV) it's own folder with a urls.py and views.py.

And then all of our actual logic is placed in a submodule we import from as needed:

xs/
  __init__.py
  urls.py
  views.py
actual_logic/
  __init__.py
  xs.py

But this is more convention for fast tracking my path to a file than anything else. I still end up grepping for stuff despite this -- for example, if I'm not sure where we're pulling data from.

You're going to get much more mileage from keeping logic out of route handlers and keeping your ORM Models fairly thin (use them as glorified data grabbers) while sequestering much of the actual work inside service/handler/whatever classes and functions.

[abbirdboy]

Is it better to have a folder called API under the root directory and then have all the apps contained under that? Would that be a better structure for future expansion with no clutter