On 10 Sty, 18:42, "uber.ubiwanken...@gmail.com" <uber.ubiwanken...@gmail.com> wrote: > Hi all, > I've created a directory for all my usable apps, configured PYTHONPATH > and everything's fine. > But I got a problem when some apps release new versions and I want to > update them on my hd. Why? What is the problem?
> Plus, usually I get the svn version of an app to quickly update it. svn up, and...? > How do you resolve this kind of problem? But what is your problem? > Do you use virtualenv or django-reusableapps? Yes, and? > What is the right way to deal with it in a production environment? When you deploy an application (in Django world - "project") onto production env, then you should use specific revision of your own application which will contain specific revisions of external applications. For example Django 1.0.2 or Django rev. xxx (i mean svn revision number), photologue rev. xxx etc. Then your application in version 1.0 is build of your code and external apps in specific versions. When you create version 1.1 then you will probably include other versions of externals (for example when there are new ones). Do you use any SCM like svn? If you use svn then for external apps you can use so called "vendor branches". eXt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
