Comments for intuitive engineering http://dougmunsinger.com doug munsinger Sat, 20 Nov 2010 22:01:43 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on svnadmin.pl – perl cgi script to manage svn over apache by Simple web-frontend for remote svn administration? http://dougmunsinger.com/2009/05/svnadmin.html/comment-page-1#comment-12505 Simple web-frontend for remote svn administration? Sat, 20 Nov 2010 22:01:43 +0000 http://dougmunsinger.com/?p=738#comment-12505 [...] (or a small number of scripts) which use Perl or PHP. I found svnadmin (From Jochen Hoenicke) or svnadmin.pl (From doug munsinger), but was hoping to find something with a larger user community or which has [...] [...] (or a small number of scripts) which use Perl or PHP. I found svnadmin (From Jochen Hoenicke) or svnadmin.pl (From doug munsinger), but was hoping to find something with a larger user community or which has [...]

]]> Comment on resolution from hostgator… sort of by doug http://dougmunsinger.com/2008/09/resolution-from-hostgator-sort-of.html/comment-page-1#comment-6465 doug Thu, 15 Apr 2010 12:15:02 +0000 http://dougmunsinger.com/?p=346#comment-6465 I've had an excellent experience with Dreamhost, the hosting company I went to from Hostgator. Dreamhost leaves the SSL protocol for my domains completely alone, has better pricing over the long term, and has been responsive for the rare support issue that comes up. I’ve had an excellent experience with Dreamhost, the hosting company I went to from Hostgator. Dreamhost leaves the SSL protocol for my domains completely alone, has better pricing over the long term, and has been responsive for the rare support issue that comes up.

]]> Comment on subversion compile and install as non-privileged user… by doug http://dougmunsinger.com/2009/04/subversion-compile-and-install-as-non-privileged-user.html/comment-page-1#comment-4274 doug Tue, 29 Sep 2009 01:42:11 +0000 http://dougmunsinger.com/?p=656#comment-4274 I believe you would copy the new libraries and binaries into the location expected, along with the new svn. i would suggest you do this step by step on a test server first and then move to the production setup, and while doing the test instances watch for methods/steps that allow you to back out and return to the original install with certainty. That sinking feeling when things don't quite work and when you don't have a route back is not something I want to experience (again). I believe you would copy the new libraries and binaries into the location expected, along with the new svn.

i would suggest you do this step by step on a test server first and then move to the production setup, and while doing the test instances watch for methods/steps that allow you to back out and return to the original install with certainty. That sinking feeling when things don’t quite work and when you don’t have a route back is not something I want to experience (again).

]]>