Re: upgrading from 6.0.20 to 6.0.35
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hassan, On 12/9/11 11:38 AM, Hassan Schroeder wrote: On Thu, Dec 8, 2011 at 11:13 PM, Pid * p...@pidster.com wrote: Yes, but we still usually recommend starting afresh each time. It should relatively simple, just make a backup copy of each file you edit, first. Somewhat OT, but I would like to recommend git (http://git-scm.com/) as the *perfect* way to manage configurations. Or, at least *some* revision-control-tracking mechanism: CVS, Subversion, git, Mercurial, whatever. Saunder Temme says that putting your server configuration under revision control is a recommended security procedure: http://people.apache.org/~sctemme/ApconNA2011/Hardening%20Enterprise%20Apache%202011.pdf Hmm... that presentation doesn't say it, but he's definitely mentioned it in the past. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7mWdUACgkQ9CaO5/Lv0PCODwCffOKuKRxJxnoT+bMLaXaaWWUN pkYAn1vhEztP/X/FqvbYU1ahOJ+jawR5 =HhaS -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: upgrading from 6.0.20 to 6.0.35
- Original Message - From: Christopher Schultz ch...@christopherschultz.net To: Tomcat Users List users@tomcat.apache.org Cc: Sent: Monday, December 12, 2011 11:45 AM Subject: Re: upgrading from 6.0.20 to 6.0.35 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hassan, On 12/9/11 11:38 AM, Hassan Schroeder wrote: On Thu, Dec 8, 2011 at 11:13 PM, Pid * p...@pidster.com wrote: Yes, but we still usually recommend starting afresh each time. It should relatively simple, just make a backup copy of each file you edit, first. Somewhat OT, but I would like to recommend git (http://git-scm.com/) as the *perfect* way to manage configurations. Or, at least *some* revision-control-tracking mechanism: CVS, Subversion, git, Mercurial, whatever. I cannot add enough +1 to this. Security procedure or no, managing more than a few servers without version control and software release management is asking for disaster. Saunder Temme says that putting your server configuration under revision control is a recommended security procedure: http://people.apache.org/~sctemme/ApconNA2011/Hardening%20Enterprise%20Apache%202011.pdf Hmm... that presentation doesn't say it, but he's definitely mentioned it in the past. - -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: upgrading from 6.0.20 to 6.0.35
On Thu, Dec 8, 2011 at 11:13 PM, Pid * p...@pidster.com wrote: Yes, but we still usually recommend starting afresh each time. It should relatively simple, just make a backup copy of each file you edit, first. Somewhat OT, but I would like to recommend git (http://git-scm.com/) as the *perfect* way to manage configurations. It's an unobtrusive, simple way to track your changes without the clutter of extraneous backup files. And you can easily keep remote repository copies as well. FWIW, -- Hassan Schroeder hassan.schroe...@gmail.com http://about.me/hassanschroeder twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
upgrading from 6.0.20 to 6.0.35
hi, how easy is to upgrade? can i use the server.xml in 6.0.20 without changes in 6.0.35? thanks, angelo -- View this message in context: http://old.nabble.com/upgrading-from-6.0.20-to-6.0.35-tp32938729p32938729.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: upgrading from 6.0.20 to 6.0.35
On 9 Dec 2011, at 06:28, AngeloChen angelochen...@gmail.com wrote: hi, how easy is to upgrade? can i use the server.xml in 6.0.20 without changes in 6.0.35? thanks, Yes, but we still usually recommend starting afresh each time. It should relatively simple, just make a backup copy of each file you edit, first. NB it's often easier to remove all of the XML comments once you're in production, so you can see the doc content more clearly. p angelo -- View this message in context: http://old.nabble.com/upgrading-from-6.0.20-to-6.0.35-tp32938729p32938729.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
