On Thursday 26 April 2007 9:12 pm, Ray wrote:
> I am setting up a new web server that must host data from an existing
> webserver. We've never had an organized folder structure for private data,
> (passwords, secure data, etc) and I'm trying to change that.
> there are currently a number of virtual sites all handled through apache
> virtualhosts. all (or at least most) users must have ftp access.
> my original thought was this:
> contains a soft link to
> and the ftpchroot is
> this doesn't work like I wanted it to. I can't follow the link with an ftp
after posting, I decided I'm going to do it this way, and hope the other
developers didn't cheat too bad. I think this is the right way.
> obviously the best solution would be
> which contains
> with domain1 as the ftp root
> and pub_data as the http root,
> but I'm not the developer of all the sites, and I don't want to have to
> trouble shoot other peoples possibly incorrectly written sites (hard coded
> path structures)
> What can you suggest as my best solution?
> firstname.lastname@example.org mailing list
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"