Ah, but using KIDS to move what you mean to move means you always have a record of what you've installed/changed in production. Better to know what you've changed in production than to change something and forget what it was!
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg Kreis Sent: Monday, September 12, 2005 5:30 PM To: [email protected] Subject: Re: [Hardhats-members] Re: VistA installation and backups Indeed. This seems the most ideal, but I guess there may be constraints precluding this approach. If it was me, I'd definitely opt for this since moving KIDs back and forth would be a sure way to 'forget something' and then you spend time debugging what is not really supposed to be a problem. Kevin Toppenberg wrote: Why not create a secure connection so that you can work on the system from home. I.e. via SSH? Kevin On 9/12/05, K.S. Bhaskar <[EMAIL PROTECTED]> wrote: Are you talking about VistA on GT.M or Cache (and I would presume Windows vs. Linux for the latter). With GT.M, setting up a VistA configuration on one machine and moving it another would be operationally trivial (you would need to presumably rename the second machine). That's how I create the OpenVistA SemiVivA releases. It takes a few minutes and a few shell commands, but that's all. Taking a database + routines snapshot of a live (i.e., operational) VistA machine (which I don't do) would also be pretty straightforward. -- Bhaskar On Mon, 2005-09-12 at 15:08 -0500, Dr. Schrom wrote: If the release of VOE is 'on hold' (like Kevin's thought about big money from private EMR vendors), I guess I'm going back to work on installing FOIA VistA. Two questions I haven't found addressed in the archives: 1. Is there a way to install VistA and then package that installation and copy it to another machine? For example to install it on a machine in my office but burn a disk to take the 'installation' home (or move it to a laptop for the same purpose) to work on it at home, and do the reverse the next day? There are so many steps in configuring VistA that I have not managed to replicate the same installation on two different computers. I would like to keep the 'production' machine in one place, but I'd get yelled at if I stayed in the office all night working on VistA, and I can't get much done between patients during the day. 2. Which VistA directory or directories should be a part of a daily backup? Would a 'restore' from that backup serve re: #1? Mike Schrom ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members -- Greg Kreis http://www.PioneerDataSys.com "You are today where your thoughts have brought you, you will be tomorrow where your thoughts take you." (James Lane Allen) ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
