RE: [development] Distilling distributions from configured sites.
I don't know what the "sites/all thing" is, but I like having all my site specific themes, modules, and files under sites/domain/. What I would like to see in an installer is a series of checkboxes: [ ] Create files directory at sites/domain/files [change] [ ] Create themes directory at sites/domain/themes [change] [ ] Create modules directory at sites/domain/modules [change] I think that gives the user the most flexibility. I especially like the idea of it pre-creating the files directory. Unfortunately, I didn't decide that files would be better in their own site dirs until recently and now I'm stuck. I want to move them but the fact that no one has answered me on http://drupal.org/node/76924 in nearly a week has me scared to try it. LOL Michelle On 8/9/2006 10:59:54 AM, Jeff Eaton (jeff@viapositiva.net) wrote:
Eliminates the need *in many cases*... But certainly not in all cases. I can't imagine someone who wants to put together a web site not putting at least a few custom modules in, or one or two downloaded (or customized) themes.
--Jeff
-----Original Message----- From: Khalid B [mailto:kb@2bits.com] Sent: Wednesday, August 09, 2006 9:53 AM To: Adrian Rossouw Cc: development@drupal.org Subject: Re: [development] Distilling distributions from configured sites.
You are right.
I think the sites/all thing that is in HEAD now eliminates the need for site specific modules and themes, and keeps things separate from core as well (for upgrades).
Michelle Cox wrote:
I don't know what the "sites/all thing" is, but I like having all my site specific themes, modules, and files under sites/domain/. What I would like to see in an installer is a series of checkboxes:
[ ] Create files directory at sites/domain/files [change] [ ] Create themes directory at sites/domain/themes [change] [ ] Create modules directory at sites/domain/modules [change]
I think that gives the user the most flexibility.
I especially like the idea of it pre-creating the files directory. Unfortunately, I didn't decide that files would be better in their own site dirs until recently and now I'm stuck. I want to move them but the fact that no one has answered me on http://drupal.org/node/76924 in nearly a week has me scared to try it. LOL
Michelle
On 8/9/2006 10:59:54 AM, Jeff Eaton (jeff@viapositiva.net) wrote:
Eliminates the need *in many cases*... But certainly not in all cases. I can't imagine someone who wants to put together a web site not putting at least a few custom modules in, or one or two downloaded (or customized) themes.
--Jeff
-----Original Message----- From: Khalid B [mailto:kb@2bits.com] Sent: Wednesday, August 09, 2006 9:53 AM To: Adrian Rossouw Cc: development@drupal.org Subject: Re: [development] Distilling distributions from configured sites.
You are right.
I think the sites/all thing that is in HEAD now eliminates the need for site specific modules and themes, and keeps things separate from core as well (for upgrades).
you got a response now.
On Wed, 9 Aug 2006, Michelle Cox wrote:
I don't know what the "sites/all thing" is, but I like having all my site specific themes, modules, and files under sites/domain/. What I would like to see in an installer is a series of checkboxes:
[ ] Create files directory at sites/domain/files [change] [ ] Create themes directory at sites/domain/themes [change] [ ] Create modules directory at sites/domain/modules [change]
I think that gives the user the most flexibility.
Try to think of you as a Drupal beginner. Do you understand what these options mean? Why are you presented with these options in the first place? Goba
Ideally the installer would have basic and advanced installs. Basic is, well, basic (hate to reuse the example, but it should be Wordpress-stupid). Advanced can have a bunch of options in a collapsable group. On 8/9/06, Gabor Hojtsy <gabor@hojtsy.hu> wrote:
On Wed, 9 Aug 2006, Michelle Cox wrote:
I don't know what the "sites/all thing" is, but I like having all my site specific themes, modules, and files under sites/domain/. What I would like to see in an installer is a series of checkboxes:
[ ] Create files directory at sites/domain/files [change] [ ] Create themes directory at sites/domain/themes [change] [ ] Create modules directory at sites/domain/modules [change]
I think that gives the user the most flexibility.
Try to think of you as a Drupal beginner. Do you understand what these options mean? Why are you presented with these options in the first place?
Goba
The installer already has a collapsed "Advanced" field set. All this optional stuff could go there, and usability would still be good.
i think the install.php should still be only getting the system up and running. I like how the installer takes you to wherever the install profile asks (ie: post-install). I would like to see the system not be accessible at all until post-install has been completed, actually. So that you can fire the installer in the back end, and then point someone to the site to complete the form with their site specific settings. On 8/10/06, Khalid B <kb@2bits.com> wrote:
The installer already has a collapsed "Advanced" field set.
All this optional stuff could go there, and usability would still be good.
basic installs would have no post-installer. On 8/10/06, Adrian Rossouw <adrian@bryght.com> wrote:
i think the install.php should still be only getting the system up and running.
I like how the installer takes you to wherever the install profile asks (ie: post-install).
I would like to see the system not be accessible at all until post-install has been completed, actually. So that you can fire the installer in the back end, and then point someone to the site to complete the form with their site specific settings.
On 8/10/06, Khalid B <kb@2bits.com> wrote:
The installer already has a collapsed "Advanced" field set.
All this optional stuff could go there, and usability would still be good.
On Wed, August 9, 2006 12:39 pm, Michelle Cox said:
I don't know what the "sites/all thing" is, but I like having all my site specific themes, modules, and files under sites/domain/. What I would like to see in an installer is a series of checkboxes:
sites/all is a new minor feature in current CVS that adds a 3rd place where modules and themes can be stored. In addition to /modules/ and sites/sitename/modules/, they can also be placed in /sites/all/modules/. Modules in /modules/ and /sites/all/modules/ will be available to all sites, while modules in /sites/sitename/modules/ are site-specific. It's primary purpose is that there is now no excuse to put modules in /modules/ that don't come with the core system. Leave that directory pure and pristine! The same applies to theme directories. ALL installation-specific stuff can now go under /sites/. (This was one of the decidedly few patches I had time to contribute myself recently, so I mention it where I can. <g>) --Larry Garfield, who wishes he had more time to work on Drupal
participants (7)
-
Adrian Rossouw -
Darrel -
Earl Dunovant -
Gabor Hojtsy -
Khalid B -
Larry Garfield -
Michelle Cox