4 ms·
Doesn't manage.py have expectations of where things are? I also think it depends on the project. If your project has 12 apps, you might want to do it around th
by projectramo 8y ago
Doesn't manage.py have expectations of where things are?
I also think it depends on the project. If your project has 12 apps, you might want to do it around the apps. If it has 3, you might do it around data, domain, and interfaces.
Why data domain and interfaces, btw?
- theptip 8y ago> Doesn't manage.py have expectations of where things are? Yes, but this is all configurable/remappable; FTA: > One last note to add is that this project structure results in fewer INSTALLED_APPS entries. The data/ directory, containing the models, and the interfaces directories, containing templates, static files, management commands, etc., all need to be included as entries. Related; here's an example of an extreme surgery resulting in a single-file Django app: https://simpleisbetterthancomplex.com/article/2017/08/07/a-minimal-django-application.html https://simpleisbetterthancomplex.com/article/2017/08/07/a-m...
- aequitas 8y agomanage.py is just an convention about the entrypoint to your application, and for manage.py your application is basically just a python modules that are imported (yours and 3rd party app modules). So in the end it boils down to what is in your settings.py regarding 'installed apps' and if manage.py can find and import your settings.py, which is dictated by DJANGO_SETTINGS_MODULE.