how to layout a "big" project in django 1.4 - best practices ?

268 views
Skip to first unread message

Michael Palumbo

unread,
May 15, 2012, 6:13:29 PM5/15/12
to django...@googlegroups.com
Hi,

I have found lots of posts on how organizing a kinda big project with Django =<1.3 but I was wondering what could be the best option with Django 1.4 since the default layout has changed.

I have found just this post on the internet talking about structuring a django 1.4 project: http://www.deploydjango.com/django_project_structure/index.html
What do you think?

Please feel free to share your points of views and/or explain how you handle it.

Thanks

Phang Mulianto

unread,
May 16, 2012, 12:42:40 AM5/16/12
to django...@googlegroups.com

Hi..

For the app, i like to use loose couple method from project dir so i can reuse and plug my app in other project easily.

I learn it from a book call practical django apps.

And i want ask about settings.py,  if we make the settings become a folder and put dev.py, prod.py,  any step to make manage.py know which one to load. Seems there is no info about it in the blog.

Btw i stil using django 1.3

Thanks for the share

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/7G089jM6W6gJ.
To post to this group, send email to django...@googlegroups.com.
To unsubscribe from this group, send email to django-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Michel Thadeu Sabchuk

unread,
Sep 26, 2012, 9:59:30 AM9/26/12
to django...@googlegroups.com

Hi Guys,
 

And i want ask about settings.py,  if we make the settings become a folder and put dev.py, prod.py,  any step to make manage.py know which one to load. Seems there is no info about it in the blog.

I often create a settings module like above:

settings
-->__init__.py
------>base.py
------>custom.py

The __init__ file imports everything from base and custom, custom imports everything from base and can replace any base settings. This way I can put the __init__ and base files in the repo but keep custom not tracked, since it is environment specific.

What are you doing about the project name? I am using the project folder as the trunk root, so, doesn't matter what will be his name. The default app generally is the project name but we prefer to call it main, so every project have the same layout, with the same default app... What do you think about it?

Best regards,

Michel Sabchuk
Reply all
Reply to author
Forward
0 new messages