Giancarlo F. Berner ha scritto:
Hi Matteo
Hi Giancarlo, nice to hear you :-)
In larger projects we typically "separate" Dev Servers, Test Servers and
Production Servers.
I want to separate them too...
We are going to implement this architecture:
DEV author --> DEV public (one machine)
TEST author --> TEST public (two machines)
PROD author --> PROD public 1 + PROD public 2 (three machines)
One option is to use the Packager Tool. However, you can also "Export"
the config tree. The third option is to create a simple module and use
the "Version Handler" to update the hierarchy.
Within servers (e.g. within the "Test Server") you can use activation.
However, this only works for "Repository Content" (e.g. Code and
Resource files are not included).
For resource file we deploy jars on all servers..
We also follow Rubens "Instance Chain", because each and every change
has to be tested prior to go to production. If you use "activation", be
aware that you might have multiple subscribers, so you have to
enable/disable them for special kind of activations.
This can be a problem, of course.. I've not even understood how can I
achieve to separate activations.
How can I do to activate <data> content over SUBSCRIBER1 + SUBSCRIBER2
but I need to activate <website> content ONLY over SUBSCRIBER2? How can
I differenciates them?
I've tried to use subscriptions, but I've seen that for some reasons I
receive "Not EE subscriber" error, when I try to activate content over
another author instance..
That's why we in
most cases have "physical" replication, by exporting a hierarchy or
creating packages.
Packages are very useful, because you can also restore them and you can
include files as well.
Yes, I think for Major Deploy packager can be useful.
You say files... but how can I export files? If I choose "files" an
empty tree is open on button click..
Cheers
Giancarlo
Thanks a lot, Giancarlo..
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
