On Wed, August 9, 2006 9:35 am, Khalid B said:
On 8/9/06, Morbus Iff <morbus@disobey.com> wrote:
Another point I came across, is the files directory. I believe the installer should try and create it, and I also believe the distributions should be able to have default files that are copied to the directory.
yes. this is sticks out like a sore thumb given how smooth install is now.
I mentioned this to eaton a little:
* the installer should save to sites/domain.com/settings.php.
It already does that, sort of, if the directory for the domain is created and if the settings.php is the default one.
So, if what you are saying is it should create domain.com directory and settings.php, then I am with you on this.
Long term, using domain.com is far better than default, since you can move from multi site to single site and vice versa seamlessly. If you use default, there is a lot of work involved and hence not seamless.
What about moving from a test site to a live site, however? I do that all the time. We should have clear migration instructions available in a provided readme or even in settings.php itself, as well as on the site, if it's not going to be automated.
* the installer should pre-create sites/domain.com/files/
Fully agree.
+1
If the Apache user cannot create the directory, then it should tell the user to do so.
While we are at it, why not add modules and themes as empty directories too?
+1 I don't know if we want it to create sites/all/modules et al, however. I can see arguments both directions. --Larry Garfield