#Database Security

9 messages · Page 1 of 1 (latest)

jagged field
#

I'm still learning the framework, and I've been getting mixed messages from different tutorials.
So would each app made with "startapp" be it's own separate application, or just another part of the broader application.
My second question is if I should create an app names "core" and then create a second one, and import database info from the "core" app?

Any help is appreciated 🙂

wet zenith
#

And what the question has to do with security?
"App" is term that django uses for python modules of which your project consists and which are added through INSTALLED_APPS settings for a few features like models, templates and static files discovery

#

Project can consists of one or more apps, django itself comes with a number of apps which you see in settings by default

calm osprey
#

In general my recommendation is to not create a lot of apps. It's just messy.

oak wave
#

You can go very far with just one big app, and modularize its internal folder structure as needed, imho.

winter cedar
#

And don't confuse "app" with "database"—one Django install generally talks to a single database, regardless of how many "apps" it has, they all share that one database

jagged field
wet zenith
#

That's are very different things

#

Models can be imported without much trouble, but if you heavily cross-refer between apps that's likely an indicator of poor code structure