[Date Prev][Date Next][Thread Prev][Thread Next][Minivend by date
][Minivend by thread
]
Re: Simple Upgrade Path? Docmentation?
****** message to minivend-users from "Mr. Christopher F. Miller" <cfm@maine.com> ******
On Sat, May 15, 1999 at 08:38:59AM +0100, Dirc Evans wrote:
> ****** message to minivend-users from Dirc Evans <dirc@workx.co.uk> ******
>
> Comrades!
>
> With different versions of MV coming out regularly with added functionality
> and bug-fixes, it would suggest that many users who download are probably
> doing so to upgrade an existing installation. However, there is absolutely
> no documentation on any upgrade processes.
We usually maintain different versions of minivend in /var/ as
/var/mvend<n.nn>. We do compile vlink for each one; that's easy.
In our case the catalogs live in /var/mv/<catalog_name>.
That lets us keep different minivends going at once. The vlink
itself we keep in /usr/cgi/ but that is **very** web server
dependant. We just link to it from any particular catalog's web
space.
To convert a catalog it is "simply" a matter of changing the symlink
to point to the new vlink AND <ahem>testing the catalog</ahem>. There
are enough developments in /scan/ and various perl modules, Storable
for instance, that testing is essential.
cfm
--
Christopher F. Miller, Publisher cfm@maine.com
MaineStreet Communications, Inc 208 Portland Road, Gray, ME 04039
1.207.657.5078 http://www.maine.com/
Database publishing, electronic commerce, office and internet integration.
-
To unsubscribe from the list, DO NOT REPLY to this message. Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list
