From: Carsten K. <car...@us...> - 2003-12-07 15:56:09
|
On Saturday, December 6, 2003, at 10:05 pm, Dan Sawyer wrote: > All, > > After making many out of the gate errors I got phpwiki to run on my > local system. > > Wow! It is great!! > > I then promised a group I would make this great tool available to > them. I thought the install would take 15 minutes. The only tool > available is ftp. First the directory structure causes many manual > copy steps. > > That was the easy part. Now the site seems to manually override my > permissions and install every thing with 644 instead of 664. There is > no global change in ftp. > > 1. Is there an iterative smart ftp client that can make this easier? > > 2. How do others do this? (it really limits the middle tier user such > as myself) > > 3. What am I missing?? > > Dan Hi Dan, I use ncftp or the perl script ftpsync (ftpsync.sf.net) to update my remote wikis. Unfortunately with ftp one is restricted by the permissions the server gives gives. ncftp allows you to do things like chmod g+w, but many servers do not allow it or do not support it. In that case your only recourse is to contact the ftp-server administrator to change write access permissions of any individual files. :/ ncftp is smart enough to avoid uploading a file with the same modification date, this helps a bit. It also allows recursive gets and puts, so you can do "put -r phpwiki" etc. When I have many changes to upload, I use the ftpsync script. It takes a while to run because it traverses the entire directory tree but has worked flawlessly for me so far. There are other ftp synchronization scripts if ftpsync isn't your taste. If you can arrange it with the server admin, the easiest I found is to use scp (secure copy). A shell with ssh is handy to login for those quick fixes or tweaks with a text editor on the server pico/nano/emacs etc. If the admin won't go for scp and/or ssh then you're simply stuck with ftp. Carsten |