<br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style=""><div class="Ih2E3d"><div><div>On 09 Dec 2007, at 6:30 AM, Larry Garfield wrote:
</div><br><blockquote type="cite"><p style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">
Emphasis on the "properly". :-)<span> </span>I had been going with the conventional wisdom<span> </span></font></p> <p style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">
of sites/<site>/files, but when I went to merge two sites into a multi-site<span> </span></font></p> <p style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">
to deploy them realized that wouldn't work; the path that is stored into the<span> </span></font></p> <p style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">
files table is then bound to the domain the site is on, which is no good<span> </span></font></p> <p style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">
because the domain changes from staging to production.<span> </span>So if we document<span> </span></font></p> <p style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">
sites/default/files for single-site installs, we need to in the same breath<span> </span></font></p> <p style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">
document to *not* use the sites/ directory for multi-site installs unless you<span> </span></font></p> <p style="margin: 0px;"><font style="font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; font-size: 12px; line-height: normal; font-size-adjust: none; font-stretch: normal;" face="Helvetica" size="3">
want to make moving to a new server to be a PITA.</font></p> </blockquote></div></div></div></blockquote><div><br>Perhaps a decoupling of the paths from the domain is in order.<br><br>There is a way to do it today with symlinks: under "sites/" we have s1, s2, s3,
<br>...etc. One directory per site. Then files would be "sites/s1/files". A symbolic<br>link then makes s1 be <a href="http://site1.example.com">site1.example.com</a>, and s2 <a href="http://www.example.com">www.example.com
</a> and s3<br>is <a href="http://example3.com">example3.com</a>, ...etc.<br><br>If you then decide to use .net instead of .com for s1, the file paths do not change<br>at all. They remain the same.<br><br>What this does is have one level of indirection, so we don't run into these
<br>hard coded domains in file path names.<br><br>Maybe we should formalize that as the advocated solution. This works for all<br>UNIX like systems. Not sure about those hosting/developing on Windows though.<br></div></div>