Electronics & Programming

develissimo

Open Source electronics development and programming

  • You are not logged in.

#1 Dec. 10, 2010 01:26:51

a.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

Django Team Project Best Practices


I have been using Django for a little over two years as a freelance
developer. I am currently working at a company where I am at the
beginning stages of a two-person Django app. I have worked on group
projects before, quite some time ago, as an html editor. I definitely
don't have experience at developing a two-person Django project. I
have he envisioned initiating a django project, initiating an empty
app under that project, establishing template and static folders in
the project. After then I figured I would add the project to a github
repository then have my co-worker clone the project. After that we
could work away on separate branches and merge when ready. My co-
worker wants to have the repository only have the app part of the
project and the app will contain media and static folders. Each
developer would have a project root with only manage.py, urls.py and
the clone app. His thinking that this fits the Django way of doing
things more closely, but I don't see it this way and the only
explanation I can give is that I would be having all of the project's
files and folders in the standard django project folder. I would
greatly appreciate hearing from anyone with insight or advice. Thanks
in advance.

--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group athttp://groups.google.com/group/django-users?hl=en.

Offline

#2 Dec. 10, 2010 01:33:06

satyandra b.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

Django Team Project Best Practices


if you have many modules in projects then set one app for each module will
be easy but still that app will be part of your django project, for example
accounts, registration, userprofile and others if you your project is
concern about users but if your project is small enough you can go with one
app as well.

having different app in same project give you proper hierarchy for the
project, and it is east to handle.



On Fri, Dec 10, 2010 at 6:56 AM, acat...@gmail.com <acat...@gmail.com>wrote:

> I have been using Django for a little over two years as a freelance
> developer. I am currently working at a company where I am at the
> beginning stages of a two-person Django app. I have worked on group
> projects before, quite some time ago, as an html editor. I definitely
> don't have experience at developing a two-person Django project. I
> have he envisioned initiating a django project, initiating an empty
> app under that project, establishing template and static folders in
> the project. After then I figured I would add the project to a github
> repository then have my co-worker clone the project. After that we
> could work away on separate branches and merge when ready. My co-
> worker wants to have the repository only have the app part of the
> project and the app will contain media and static folders. Each
> developer would have a project root with only manage.py, urls.py and
> the clone app. His thinking that this fits the Django way of doing
> things more closely, but I don't see it this way and the only
> explanation I can give is that I would be having all of the project's
> files and folders in the standard django project folder. I would
> greatly appreciate hearing from anyone with insight or advice. Thanks
> in advance.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@googlegroups.com>
> .
> For more options, visit this group at
>http://groups.google.com/group/django-users?hl=en.
>
>

--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group athttp://groups.google.com/group/django-users?hl=en.

Offline

#3 Dec. 10, 2010 02:04:16

R.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

Django Team Project Best Practices


On Dec 9, 8:26 pm, "acat...@gmail.com" <acat...@gmail.com> wrote:
> I have been using Django for a little over two years as a freelance
> developer.  I am currently working at a company where I am at the
> beginning stages of a two-person Django app.  I have worked on group
> projects before, quite some time ago, as an html editor.  I definitely
> don't have experience at developing a two-person Django project. I
> have he envisioned initiating a django project, initiating an empty
> app under that project, establishing template and static folders in
> the project.  After then I figured I would add the project to a github
> repository then have my co-worker clone the project.  After that we
> could work away on separate branches and merge when ready.  My co-
> worker wants to have the repository only have the app part of the
> project and the app will contain media and static folders.  Each
> developer would have a project root with only manage.py, urls.py and
> the clone app.  His thinking that this fits the Django way of doing
> things more closely, but I don't see it this way and the only
> explanation I can give is that I would be having all of the project's
> files and folders in the standard django project folder.  I would
> greatly appreciate hearing from anyone with insight or advice.  Thanks
> in advance.


His reasoning sounds very odd to me. What about sharing stuff between
different apps? There's nothing in django that says a single app
should be in a repo. The point of an app is that it's portable and can
be moved around and other apps can use parts of it as needed. Repo
setup depends on what changes you will need to share, if you're
absolutely sure you'll only need to work on one app and it won't use
anything from other apps, and you won't need to add custom app
settings to settings.py, I guess it's ok but I don't see the point.

For what its worth, I've been working with repos that contained django
projects in two places and it works just fine. (and in fact it
wouldn't work otherwise for the reasons I mentioned.)

--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group athttp://groups.google.com/group/django-users?hl=en.

Offline

#4 Dec. 10, 2010 06:06:07

Kenneth G.
Registered: 2009-11-02
Reputation: +  0  -
Profile   Send e-mail  

Django Team Project Best Practices


On Thu, 2010-12-09 at 17:26 -0800, acat...@gmail.com wrote:
> the only
> explanation I can give is that I would be having all of the project's
> files and folders in the standard django project folder.

that is correct - in a project everyone has to be able to see what
everyone else is doing - or how would the project run?? Maybe in a huge
project on something ultra secret, the other approach would be feasible.
--
regards
Kenneth Gonsalves

--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group athttp://groups.google.com/group/django-users?hl=en.

Offline

Board footer

Moderator control

Enjoy the 12th of December
PoweredBy

The Forums are managed by develissimo stuff members, if you find any issues or misplaced content please help us to fix it. Thank you! Tell us via Contact Options
Leave a Message
Welcome to Develissimo Live Support