This is just an invitation to participate in django-users thread. I'm
sure this will be very useful to many people moving to django from
ruby on rails and php mvc frameworks.
The thread is here:
Thanks,
Sebastian Macias
digital-telepathy inc.
...but it hasn't been updated in a while. If anyone comes up with
useful things, could you (or them) update that page?
Thanks,
Simon
On Jul 25, 11:41 am, Sebastian Macias <sebast...@sebastianmacias.com>
wrote:
> I posted this on django-users so I won't post the same here but I
> thought the actual framework developers might have excellent feedback
> on this.
>
> This is just an invitation to participate in django-users thread. I'm
> sure this will be very useful to many people moving to django from
> ruby on rails and php mvc frameworks.
>
> The thread is here:
>
> http://groups.google.com/group/django-users/browse_thread/thread/ab9e...
The setup is here:
I want to add it to the wiki but I'm not sure if the page you posted
is the most appropriated.
Any suggestions?
Sebastian Macias
http://code.djangoproject.com/wiki/BestPracticesToWorkWith3rdPartyAppsAndMakingYoursPortable
It's also available via the resources page.
http://code.djangoproject.com/wiki/DjangoResources
Best,
Sebastian Macias
On Jul 25, 11:19 am, Sebastian Macias <sebast...@sebastianmacias.com>
wrote:
> I just came up with a setup that works perfectly for me as it allows
> me to work on project specific apps as well as on portable apps
> efficiently.
>
> The setup is here:
>
> http://groups.google.com/group/django-users/browse_thread/thread/ab9e...
I don't think you meant to have the exact same directory structure for
a django project as you did for 3rd party apps, did you?
Gary
http://code.djangoproject.com/wiki/BestPracticesToWorkWith3rdPartyAppsAndMakingYoursPortable
Thanks for letting me know,
Sebastian
django_root/
genericapp1/
genericapp2/
mysite/
__init__.py
apps/
__init__.py
siteapp1/
siteapp2/
manage.py
settings.py
urls.py
I also put default templates with the apps, and override them with
project templates if need be.
If you work with several django sites, it may be desirable to have
each use their own private copies of django and generic apps, so that
individual sites can be upgraded without worrying about backwards
incompatible changes in django or generic apps. I do this with
Subversion externals.
trunk/
django/
genericapp1/
genericapp2/
mysite/
django/ (X)
genericapp1/ (X)
genericapp2/ (X)
mysite/
__init__.py
apps/
__init__.py
siteapp1/
siteapp2/
manage.py
settings.py
urls.py
All you need to do is set the python path to root/mysite/ for your dev/
production server or interactive shell. I do that with shell aliases/
scripts. Then you can still work on your generic apps within mysite,
and commit those changes directly back to the trunk version to be
utilised by other projects that track trunk, or new projects.
--Simon
On Jul 28, 5:47 am, Sebastian Macias <sebast...@sebastianmacias.com>
wrote:
> I just added it to the wiki:
>
> http://code.djangoproject.com/wiki/BestPracticesToWorkWith3rdPartyApp...