Edmund Hertle wrote:
2009/1/20 Nathan Rixham <nrixham@xxxxxxxxx>
you don't have to locally develop, you can develop however you want :) svn
is just version controlling all your files to make it easier to team work
and to rollback code. you then tag good versions of the code in svn so you
have a permanent easy to access good version of the site (which you then
copy and do what you want with, download, ftp whatever) keeps you safe :)
Yeah, I think I mix up (web)server and rep some times...
But to point out an example:
There is a script on the (develop) webserver, the same locally and of course
in the rep.
So I start working on the local copy and now want to try it. So what should
I do? Copying directly to the webserver, testing and than later after some
more work commit to the rep?
Work on the webserver directly, or set up a test environment on your
machine. You could set up a samba share or shared drive on the server,
or if it's a *nix based server, use an editor that lets you sftp (which
is "secure ftp" - like ftp but across a secure port, usually ssh).
Or other way: Start working on script, commit to rep, than update
(develop)webserver, than testing....?
Test your changes, then commit. When you look at the repo, at least you
know most of the functionality works at any point in time.
--
Postgresql & php tutorials
http://www.designmagick.com/
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
