[ic] Configuration management of store front (am I the only one that needs this)
Wed, 21 Mar 2001 21:54:18 -0800
Nobody answered my question, am I the only one that has need for this?
I will try this again to see if I get any takers...
What if I want to work on a "pending" store with proposed
changes and then when the boss says it is okay, flip a switch and it is now
the live copy? I need to flip flop between copies so that there is always a
"live shop" and a "proposed next version" shop? I am thinking that I just
copy the live directory to a backup directory, and then that is that, but
what problems will I come against? How do I keep the sales records rolling
forward, but the catalog and web site content managed by a "flip-flop" type
approach? What tables should always keep moving forward?.
In other words, using the "Akopia Three Tiered Approach"
The site designer wants to work on a proposed site and see it functioning in
a test mode before it is posted live. The we want to flip a switch and see
the new content go public, ans start working on a new version offline again
The store administrator does NOT want to go back and lose sales records, so
there is no "configuration management" need for him.
The technical implementor (poor old me) is trying to figure out how to make
Can the many Interchange tables be identified as to their function and split
out so that a version control/configuration management type system could be
put in place?
If this content configuration management feature were put in
to place, this system would rival the Vignette Story Server big boys.
What is the scope of a project that would add these features?