I suggest this structure:
myproject
- apps
- libs
- conf
- public
- settings.py
- urls.py
conf:
- production.py
- test.py
- dev.py
libs:
- all third party modules
public:
- media
- static
- admin
- django.wsgi
each app structure:
- admin
- backends
- commands
- context_
On 20 Kov, 22:10, Markus Gattol wrote:
> That does not seem to work with pip and virtual environment, does it?
> This one doeshttps://github.com/epicserve/django-environment
It does work with zc.buildout.
--
You received this message because you are subscribed to the Google Groups
"Django deve
> My company had same problem with project layout. We solved it by
> creating django-starter project. django-starter is already used by 10
> or more projects and it seems, that this solution works.
>
> https://bitbucket.org/sirex/django-starter/src
That does not seem to work with pip and virtual e
> My company had same problem with project layout. We solved it by
> creating django-starter project. django-starter is already used by 10
> or more projects and it seems, that this solution works.
>
> https://bitbucket.org/sirex/django-starter/src
That does not seem to work with pip and virtual e
On 11 Kov, 07:14, Simon Litchfield wrote:
> Who votes we should come up with a django-blessed 'official' default project
> layout / directory structure?
My company had same problem with project layout. We solved it by
creating django-starter project. django-starter is already used by 10
or more
> I think, it's a good idea to add new option to startapp command
There is django-extensions which has a create_app command that takes a
--template switch.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
On 18/03/11 04:59, Alex Kamedov wrote:
> On Thu, Mar 17, 2011 at 9:26 PM, Calvin Spealman wrote:
>
>> -1 On django manipulating PYTHONPATH
>
> +1 On encouraging people to keep their applications out of their project!
>>
> I think, it's a good idea to add new option to startapp command for create
On Thu, Mar 17, 2011 at 9:26 PM, Calvin Spealman wrote:
> -1 On django manipulating PYTHONPATH
+1 On encouraging people to keep their applications out of their project!
>
I think, it's a good idea to add new option to startapp command for create
Django application out the project and has structur
On Fri, Mar 18, 2011 at 12:05 AM, Carl Meyer wrote:
>
>
> On 03/17/2011 05:36 AM, Tom Evans wrote:
>> I strongly disagree here. Django shouldn't be doing magic with my
>> PYTHONPATH, if I want stuff in my PYTHONPATH, I'll darn well put it
>> there.
>
> Hear, hear! I'm only a weak +0 on the entire
-1 On django manipulating PYTHONPATH
+1 On encouraging people to keep their applications out of their project!
On Thu, Mar 17, 2011 at 1:08 AM, Tai Lee wrote:
> If we're talking about the lowest common denominator and keeping
> things simple, this is what I think we'd have:
>
> myapp1/
> myapp2/
On 03/17/2011 05:36 AM, Tom Evans wrote:
> I strongly disagree here. Django shouldn't be doing magic with my
> PYTHONPATH, if I want stuff in my PYTHONPATH, I'll darn well put it
> there.
Hear, hear! I'm only a weak +0 on the entire idea of documenting a
"standard" project layout, as I think it'
On Thu, Mar 17, 2011 at 5:08 AM, Tai Lee wrote:
> If we're talking about the lowest common denominator and keeping
> things simple, this is what I think we'd have:
>
> myapp1/
> myapp2/
> myproject/
> -django.wsgi.sample
> -manage.py
> -management/
> --commands/
> ---myproject_mycommand.py.sample
If we're talking about the lowest common denominator and keeping
things simple, this is what I think we'd have:
myapp1/
myapp2/
myproject/
-django.wsgi.sample
-manage.py
-management/
--commands/
---myproject_mycommand.py.sample
-media/
--myproject/
---readme.txt
-models.py
-settings.py
-static/
--
On Mar 15, 9:46 am, Russell Keith-Magee
wrote:
> On Fri, Mar 11, 2011 at 1:14 PM, Simon Litchfield wrote:
> > Who votes we should come up with a django-blessed 'official' default
> > project layout / directory structure?
>
> Sure -- no disagreement that it would be good to have some common
> gro
I am not currently involved in Django Development, but as someone new
to Django I can endorse increased standardization & documentation in
the area of project management & structuring. I have struggled to
figure out the right set up for our project(s). I have also tried to
grapple with coupling d
On Fri, Mar 11, 2011 at 1:14 PM, Simon Litchfield wrote:
> Who votes we should come up with a django-blessed 'official' default project
> layout / directory structure?
Sure -- no disagreement that it would be good to have some common
ground with regards to project layout. All we need now is to a
Check out django-startproject from lincolnloop.com
https://github.com/lincolnloop/django-startproject
Kill off all the server configs (though some of it might be cool, like
Fabric integration), and I think it'd make for a pretty good base to
work from if this were to go into core.
On Mar 13, 9:1
I like the idea too, since I've run into a lot of situations where
some more convention here would make a decision much easier to make.
However, it isn't clear what exactly should be better defined and I
think the first step to a serious proposal would be to figure that
out.
The only example that
I'm +1 on this. Project conventions tend to be the biggest problem
when adding new people to the team, especially when it comes to
configuration management - everyone has their own way.
It would be great if there will be at least an official list of best
practices on building Django project layout
19 matches
Mail list logo
