"steve" <Us************@dbForumz.com> wrote in message
news:4_***************************************@dbf orumz.com...
Hi,
I finally figured out the best way to synch local and remote script
folders, containing many php script files.
What I used to do before was try to ftp all the changed files, etc.
which was tedious and often broke. It was also very slow.
What I do now is to pkzip the folder up, ftp the pkzip'ed data to
remote, and then unzip it there, which recreates the directories and
files.
This requires shell access at remote host.
This may be obvious to some, but certainly was not obvious to me for
the longest time.
--
Posted using the http://www.dbforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL:
http://www.dbforumz.com/PHP-approach...ict206564.html Visit Topic URL to contact author (reg. req'd). Report abuse:
http://www.dbforumz.com/eform.php?p=704860
The best situation I find is to build a development box and do all of
your work on that box, accessing the files via windows file sharing. You can
just "map the network drive" or work right via a windows share, and just
save the files when you make a change. Then you refresh the page.
Once you are happy with the result you just FTP/scp the files to the
webhost. Generally it will be best to have a development box that runs the
same OS as your host (i.e. *nix or windows) only because of the differences
in file paths between windows and *nix versions of php.
Since you're a good programmer you use relative URLs in your code and it
won't matter if the host name is an IP address (of your development box) or
the domain name (of the fully hosted site once you upload) -- and you are a
good programmer right? :) In this way, you'll probably only upload the site
a few times rather than for every little change you make.
If you don't have a spare computer around you can always use your
workstation. You'll have to install PHP and a webserver, maybe mysql. Again,
not that hard and documentation on how to do so is rampant.
If you have a *nix webhost and want to put *nix on your dev box, just
make sure to include samba (which is usually the default) and you'll be able
to, again, use window file sharing to edit you files on the fly.
No offense, but IMO anyone who works on a live site during the
development of a site is a sucker (ahem, let the flame wars begin).
Honestly, if anyone that hasn't had a local dev box, you really need to set
one up and try it out. What better reason to have your own dedicated server
and/or a great chance to learn *nix?
On a side note, if anyone HAS had a dev box and actually preferred to
use some sort of sync. solution, please tell me why as I'm interested.
-Joe
