[wp-hackers] Flexible Installation Process

[Douglas Daulton]

Shanti,

Thanks for the advice.  I'll take it into consideration.

Doug

On 11/29/05 10:55 AM, "Shanti Braford" <shantibraford at gmail.com> wrote:

> Doug,
> 
>> So, if I want every site I create to have Spam Karma, WP-Contact and 4 other
>> plugins installed, activated and configured a particular way, the
>> create_defaults() function could go along way towards this goal.
>> 
>> I was going to create a custom WP distro for myself that would address this
>> need, but it makes much more sense to have the guts of the "roll your own"
>> subsystem as part of the core.  Then, everyone can take advantage of the
>> toolset.
> 
> Sorry, slightly OT, but this has been a real timesaver for us:
> 
> Just wanted to share w/ the group how we're managing over 24 different
> installations of WordPress - on theoretically different servers.
> 
> We ended up creating a Subversion trunk with stock WordPress 1.5.2 +
> all the plugins that we need (added as needed); I think we're up to
> 15-20+ plugins.
> 
> We don't include the wp-config.php, of course, but everything else,
> including themes... is shared.  (hard-disk space is cheap these days,
> eh? =)
> 
> In retrospect, symlink may have been a better friend.
> 
> With this setup, though... in theory, all installs can be on totally
> different servers.
> 
> A little Expect + SSH + svn update magic, and the blogs are all
> updated to our latest trunk / custom WP distro.  =)
> 
> Shanti
> 
> PS: I know, the deployment purists might be cringing right about now.  =)
> 
> + http://www.cpqlinux.com/expect.html
> 
> On 11/29/05, Douglas Daulton <apakuni at gmail.com> wrote:
>> This flexible installer would be useful for more than just il8n folks.  It
>> would also prove extremely helpful for folks who maintain a wide variety of
>> WP installs on different servers for different folks.
>> 
>> So, if I want every site I create to have Spam Karma, WP-Contact and 4 other
>> plugins installed, activated and configured a particular way, the
>> create_defaults() function could go along way towards this goal.
>> 
>> I was going to create a custom WP distro for myself that would address this
>> need, but it makes much more sense to have the guts of the "roll your own"
>> subsystem as part of the core.  Then, everyone can take advantage of the
>> toolset.
>> 
>> Doug
>> 
>> On 11/29/05 7:19 AM, "Ryan Boren" <ryan at boren.nu> wrote:
>> 
>>> On Tue, 2005-11-29 at 14:20 +0330, Ali Sattari wrote:
>>>> And also i18n hackers need to have more control on initial DB insertion
>>>> values. like Links , Describtions and more ... ;)
>>>> 
>>>> Mani Monajjemi wrote:
>>>> 
>>>>> Dear Friends,
>>>>> 
>>>>> As an wordpress i18n hacker , I would like to suggest to add some
>>>>> flexibility to current installation proccess, something like what
>>>>> exists as action_hooks , but not that complex, I mean for some i18n
>>>>> porpuses it's vital to add some action_hooks in install proccess, I
>>>>> mean it would be great to include some"fixed name files" in install php.
>>>>> 
>>>>> If the files exist in specefic folder (like
>>>>> wp-includes/languages/xx/install) they would be included!
>>>>> 
>>>>> Imagine that for some i18n purposes it's vital to activate some
>>>>> plugins through the setup... It's better than a patch? isn't it?
>>>>> 
>>> 
>>> We can move the code that creates the first post, page, etc. to a
>>> create_defaults() function that can be replaced by a function of the
>>> same name loaded from wp-includes/languages/xx/install-functions.php.
>>> 
>>> Ryan
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>> 
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>> 
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers