Hello,
I read that the folder *apps* itsn't recomended.
You can see this structure: https://github.com/damianpv/skeleton_django
Best regards,
On Thursday, April 24, 2014 11:41:54 AM UTC-5, Perry Arellano-Jones wrote:
>
> It's mostly preference, use what suits you. I prefer having all of my
It's mostly preference, use what suits you. I prefer having all of my apps
in an 'apps' directory for organization's sake. I may not have an issue
keeping track of them now, but if a project gets large it could get unruly.
Anyone else that wants to contribute to any of my projects may benefit
2014-04-21 16:00 GMT+02:00 Tianyi Wang :
> Today I was reading through
> http://www.deploydjango.com/django_project_structure (great resource)
>
> The suggested folder structure for a Django project from this site is like
> below:
> (I'm only interested in layout for Django apps, not requirements
Hi,
Cool. But I see it'd work pretty nicely when you have many custom apps and
libs.
When you do "./manage.py startapp newapp", Django create the "newapp" as
the layout I'm using.
AndI have a Django site which contains four Custom apps. The layout I'm
using works fine. Just wonder is there
any
Hi,
The suggested folder structure is the standard stuff that is generally
used. I personally and all the teams I have worked with uses this
particular structure.
sent form mobile, apologies for the brevity
On Apr 21, 2014 7:30 PM, "Tianyi Wang" wrote:
Today I was reading through
http://www.dep
Today I was reading
through http://www.deploydjango.com/django_project_structure (great
resource)
The suggested folder structure for a Django project from this site is like
below:
(I'm only interested in layout for Django apps, not requirements files or
settings files)
myproject
|-- manag
6 matches
Mail list logo
