Well, as I mentioned on this list, I'm hiring an on-call professional consultant to mentor and assist with these things. Perhaps I could have him/her get me set up with SVN.
My application is already being used by the executives at my non-profit, so breaking it is not a happy thought. I will work on getting a dev directory and maybe a dev database set up. Thanks for the great reminders and suggestions! Tom On 5/1/07, Bryan Murdock <[EMAIL PROTECTED]> wrote:
On 5/1/07, Mary Shaw <[EMAIL PROTECTED]> wrote: > > Tom, > You might like to do your development/testing online in a separate > directory (or virtual host, if you can). This is mostly for after you've > released something that is being used. It's a safer way to develop - you > won't have to worry what you "break" when you save a file that might contain > a syntax error. Then, get into the habit of copying data into the "live" > directory from your development/testing area(s), or use CVS for revision > control. > I would say _and_ use CVS, not _or_. If you aren't using revision control already, you really should, you'll love it. Actually, I wouldn't say use CVS, I'd say use SVN (Subversion), or even better, one of the new distributed revision control systems. Bazaar (bzr) works best on windoze right now, I think. They are a lot easier to get up and running with. An example with bzr (it's a command-line thing only right now) cd c:\path\to\project bzr init bzr add bzr commit -m "initial import" Now you are ready to make changes to your code. bzr diff will show you what you've changed. bzr commit will commit the changes to the revision history. If you really mess up, you can go back and get previous revisions. Bryan _______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
-- Tom Haws 480-201-5476 Have a beautiful day.
_______________________________________________ Ldsoss mailing list [email protected] http://lists.ldsoss.org/mailman/listinfo/ldsoss
