PyLucid CMS Logo

fixtures in PyLucid?

page message
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
  • Blog entry doesn't exist.
Tag Cloud ajax | Amazon | Apache | Aptana | backward incompatible | blog | browser | bugfix | ColorMirror | creole | database | dbtemplates | development | django | django-reversion | django-sync | django-sync-server | 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-03 - fixtures in PyLucid?  #

Vor 2 Jahre, 6 Monate veröffentlicht, durch jens.

In v0.9 there exist not really a good way to insert initial data.

Now i added a script to create a django fixtures file from the current installation.
I also added a fixture file from a fresh "update-installation".

I hope we can use this for reimplement a comfortable installer.

(Last update: 23. April 2012, 09:42 by jens.)

tags development
0 Kommentare für 'fixtures in PyLucid?':
    Es existiert kein Kommentar für 'fixtures in PyLucid?'
Kommentar hinterlassen

django-processinfo: 7.5 ms of 275.5 ms (2.7%)