PyLucid CMS Logo

multiple site migration...

page message
  • Entry for this url doesn't exist.
tag cloud ajax | Amazon | Apache | Aptana | backward incompatible | blog | browser | bugfix | ColorMirror | creole | database | dbtemplates | development | django | django-sync | django-tagging | django-tools | django-weave | documentation | dokumentation | Eclipse | editor | encoding | fastcgi | firefox | firefox sync | formset | generic | git | html | include | IRC | javascript | linux | mysql | pip | plugin | politik | pydev | pygments | pylucid | python | release | screencast | screencasts | security | sicherheit | software | sqlite | standalone | suchmaschine | svn | test | textile | unittest | v0.10 | v0.11 | virtualenv | visible changes | web | webspace

↑ 2009-11-11 - multiple site migration...  #

Before 2 years, 3 months published by jens.

I worked today on the multiple site migration. With this you can merge existing PyLucid v0.8 installations into one v0.9 instance! The Data would be splitted by the django “sites” framework.

With Changeset 2356 you can try it. How it works explain this two pages:

There are some limits: Multiple user accounts can't merged :( So some of the update meta data with ForeignKey to the user object can be wrong, after migration.

(Last update: Nov. 20, 2009, 10:47 a.m. by jens.)

tags development | pylucid
0 comments for 'multiple site migration...':
    there exist no comment for 'multiple site migration...'
Leave a comment
tag navi developing

django-processinfo: 5.2 ms of 274.5 ms (1.9%)