afewtips.com wrote:
>
> Hi,
>
> I am starting to understand the buildout process and how to develop a site
> from the generic setup and skeleton.
> The part I don't understand is how to take a fully developed site and move
> it into production.
> For example, lets say I go through Martins comprehensive book (great
> resource) and I decide I want to move the site I developed from my local
> computer onto a different server intact - just as it sits on my local
> computer all the products and Archtypes installed and ready. Not have to
> reinstall anything. How do I do that?
> Do I export the state of the site and then import via xml import tool?
>
> Thanks for any help.
>
I suggest to first install Plone using the installer, on your production
server, so you get Python and the necessary eggs compiled and installed on
your production server. Then copy your buildout config file. Remove the
debug settings or create a modular buildout config file (with a production
part and a debug part). Re-run buildout to install the extra products you
may need.
Then either import your policy as described in Martin's book or copy over
your Data.fs file. Depends on what you have on your development server and
what you want to export/import. Copying the whole Data.fs is easier if you
have content you have developed on your test machine and you want to move it
to your production server.
The policy product is more a way to save the configuration of your Plone
development server to re-create a fresh new Plone site with the same
settings.
Francois.
--
View this message in context:
http://n2.nabble.com/Moving-a-buildout-into-production-tp759400p759488.html
Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com.
_______________________________________________
Setup mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/setup
