As discussed on #120 this provides installation instructions for the case where you are not using mezzanine-project.
This is based on top of my other pull request.
Fixed migration forms/0003 failure for Postgres
Fixed dependencies of migrations, so that './manage.py migrate' works…
… even if starting from scratch.
In README, clarified that use of 'createdb' is optional and 'syncdb' …
…and 'migrate' can be used as normal
Added installation instructions for adding Mezzanine to an existing p…
At first glance this looks great Luke, thanks so much for your help. I'll take a proper look at it soon and probably merge it all in. Thanks again :-)
I've followed these instruction to add mezzanine on top of an existing django 1.3.1 installation. I need a bit of clarification for this hunk, with static files do you mean stuff handled by django.contrib.staticfiles or just stuff that could be in MEDIA_ROOT too?
To make use of the CSS included with the default template,
copy the files from mezzanine/project_template/site_media to a folder
where they will be served as static files in your project.
Update: i've figured out myself and this are not related to django.contrib.staticfiles so is "static files" confusing only me? :)
I'm using what is now the standard Django terminology of "static files" to refer to things served under STATIC_URL.
That bit of the instructions is just pointing out that the static files for the default mezzanine template won't be available as static assets unless you actually make them so.
I'm currently working on getting staticfiles support the default for everything in Mezzanine, so over the next few days when I push up to GitHub this should be a lot simpler. It will also include this pull request, sorry it's taking so long I've gotten it merged already on my local version.