[consulting] consulting Digest, Vol 38, Issue 22
Kazys Varnelis
kazys at varnelis.net
Sat Mar 7 13:39:15 UTC 2009
unsubscribe
On Mar 7, 2009, at 8:31 AM, consulting-request at drupal.org wrote:
> Send consulting mailing list submissions to
> consulting at drupal.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.drupal.org/mailman/listinfo/consulting
> or, via email, send a message with subject or body 'help' to
> consulting-request at drupal.org
>
> You can reach the person managing the list at
> consulting-owner at drupal.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of consulting digest..."
>
>
> Today's Topics:
>
> 1. Re: New project drupal workflow (John Fletcher)
> 2. Re: Sluggishness Concern (Larry Garfield)
> 3. Re: New project drupal workflow (Victor Kane)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 7 Mar 2009 09:48:47 +0100
> From: "John Fletcher" <net at saltwebsites.com>
> Subject: Re: [consulting] New project drupal workflow
> To: "'A list for Drupal consultants and Drupal service/hosting
> providers'" <consulting at drupal.org>
> Message-ID: <004501c99f01$8928dcb0$9b7a9610$@com>
> Content-Type: text/plain; charset="us-ascii"
>
> http://drupal.org/project/plugin_manager
>
> -----Original Message-----
> From: consulting-bounces at drupal.org [mailto:consulting-bounces at drupal.org
> ]
> On Behalf Of George
> Subject: [consulting] New project drupal workflow
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 7 Mar 2009 03:43:01 -0600
> From: Larry Garfield <larry at garfieldtech.com>
> Subject: Re: [consulting] Sluggishness Concern
> To: consulting at drupal.org
> Message-ID: <200903070343.01297.larry at garfieldtech.com>
> Content-Type: text/plain; charset="iso-8859-15"
>
> Drupal Association membership does not impart any trademark license
> of any
> kind. The use of the "Drupal" trademark is subject to appropriate
> trademark
> law and depending on the usage a license requirement from Dries
> Buytaert, not
> from the Association.
>
> Although the trademark policy is still being tweaked and a final
> version has
> not yet been released, I think it's a fairly safe bet that the use
> of the
> trademark in the name of a company will require an explicit
> trademark license.
> Whether or not Dries will be inclined to grant such a license to
> this company
> in particular I cannot say, as I am not Dries.
>
> I have no knowledge of their technical prowess and will make no
> comment in
> that regard.
>
> On Thursday 05 March 2009 1:09:53 pm Steve Rasmussen wrote:
>> They are a member of Drupal association and have cleared all such
>> legal
>> issues.
>> Anyway, I just know they work well and have servers setup with
>> Drupal in
>> mind.
>>
>> nolimitsude
>>
>> On Thu, Mar 5, 2009 at 11:06 AM, Nancy Wichmann
> <nan_wich at bellsouth.net>wrote:
>>> Steve Rasmussen wrote:
>>>> I use hotdrupal.com,
>>>
>>> Although be aware that they will almost certainly run afoul of the
>>> Drupal
>>> Association trademark lawyers.
>>>
>>>
>>>
>>> Nancy
>
> --
> Larry Garfield
> larry at garfieldtech.com
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 7 Mar 2009 08:31:52 -0500
> From: Victor Kane <victorkane at gmail.com>
> Subject: Re: [consulting] New project drupal workflow
> To: "A list for Drupal consultants and Drupal service/hosting
> providers" <consulting at drupal.org>
> Message-ID:
> <ff176450903070531v70de3c69nb1d5f91c4f4213df at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Render unto Caeser what still uses CVS.
>
> What I do is, since Drupal continues in its CVS depenedency, is to
> simply do
> the following:
>
> 1. Check out every new Drupal site directly with a fresh CVS
> checkout. Let's
> suppose I am in my home directory, and I want to create a fresh Drupal
> document root in a subdirectory www. I do the following from my
> cheat sheet:
>
> $ cvs -z6 -d:pserver:anonymous:anonymous at cvs.drupal.org:/cvs/drupal
> co -d
> www -r DRUPAL-6-9 drupal
>
> Then, to update that install to a new Drupal security release it is
> a simple
> matter of running the following command from with the Drupal
> document root:
>
> www $ cvs update -dPr DRUPAL-6-10
>
> 2. Use git or SVN for the www/sites directory on down.
>
> If you like you can include a .cvsignore file in the document root:
>
> sites
> sites/default/settings.php
>
> This has proven to be for myself, the single most simple approach.
>
> Then, keep a current Drupal fresh install versioned with Git or SVN.
> Every
> time you need to update modules, you execute the following command
> (assuming
> for example that you are using the drush SVN opotion, leaving the
> drush CVS
> support unchecked) from the Drupal document root:
>
> $ drush pm refresh
> $ drush pm update --svnsync --svncommit
>
> Then just say yes.
>
> And you can keep your "master" fresh install up to date, also
> updating core
> with CVS as necessary.
>
> Victor Kane
> http://awebfactory.com.ar
> http://projectflowandtracker.com
>
>
> On Fri, Mar 6, 2009 at 8:01 PM, George <g at 8vue.com> wrote:
>
>> interesting, so each site you create is a git repos in itself and you
>> just fetch and merge with these two repos'? i've just played with git
>> for the first time today, and had similar actually! it's definately a
>> workflow i'll look into - thanks
>>
>> Abraham Williams wrote:
>>> I run 2 git repositories that i keep up to date. One contains core
>>> and
>>> the other contains my frequently used modules plus a couple. When
>>> there are updates I just update the 2 repos and then for each site I
>>> run "git pull" and all of the new changes are pulled in.
>>>
>>> It makes keeping maintaining double digit numbers of Drupal sites a
>>> lot less work.
>>>
>>> http://github.com/poseurtech/drupal-6-modules
>>> http://github.com/poseurtech/drupal-6-core
>>>
>>> Abraham
>>>
>>> On Fri, Mar 6, 2009 at 18:18, George <g at 8vue.com
>>> <mailto:g at 8vue.com>>
>>> wrote:
>>>
>>> so it's a terrible idea troy? well, it's kinda impossible to run
>>> multiple sites from one installation, when it's for different
>>> clients on
>>> different hosts (but you realise that is essentially what i'm
>>> doing
>> by
>>> checking out the dirs). and please explain, why it'd be already
>>> out
>> of
>>> date? it's easy to upgrade drupal + modules in repos as no db has
>> been
>>> built yet - heck i could set up a script to auto-update the repos
>>> daily!
>>> yet you go on to explain you do the same by cloning a site
>>>
>>> installation profiles are VERY difficult to code quickly and also
>>> poorly
>>> documented (that's why they're covered in the back of drupal
>>> books
>>> in a
>>> short chapter!). some drupal functions are available, some
>>> aren't and
>>> you need to include the relevant files as necessary. though
>>> there's the
>>> installation profile api which i haven't got around to testing
>>> yet, but
>>> apparently offers a lot of helper functions. but as for enabling
>>> modules, from what i remeber, just specifying the modules in the
>>> profile
>>> will ensure they're enabled. simply copy the default profile to
>>> a new
>>> dir, modify and test.
>>>
>>> i just hunted through the installation profiles and haven't found
>>> a base
>>> profile to work with, but take a look, there may be something
>>> there for
>>> your needs already.
>>>
>>> or, maybe someone here has a base profile they'd like to share?
>>>
>>> Christian Pearce wrote:
>>>>
>>>>
>>>> On Fri, Mar 6, 2009 at 6:08 PM, Troy Arnold <troy at zenux.net
>>> <mailto:troy at zenux.net>
>>>> <mailto:troy at zenux.net <mailto:troy at zenux.net>>> wrote:
>>>>
>>>> On Fri, Mar 06, 2009 at 11:30:24PM +0100, George wrote:
>>>>> I'm testing the idea of having a local repos of drupal and
>> the
>>>> essential
>>>>> module (and some not so essential modules) and checking
>>> out when
>>>> i start
>>>>> a new drupal project, and installing. of course this has the
>>>> negative
>>>>> that modules and drupal slowly fall out of date, but i find
>> it
>>>>> incredibly quick just to checkout, and start with the all the
>>>> modules,
>>>>> and take away what i don't want.
>>>>
>>>> It sounds to me like a pretty terrible idea to start with
>>>> something that is
>>>> already out of date. If you want a rapid start, why not
>>> just run
>>>> multiple
>>>> sites out of one Drupal install?
>>>>
>>>> Also the drush module is pretty darn spiffy for quick module
>>> installs.
>>>>
>>>>
>>>> Do you have an example of this?
>>>>
>>>>
>>>>
>>>>> i'm thinking about combining this with an install profile to
>>>>> automatiically enable the core essential modules cck /
>>> views etc to
>>>>> remove an extra layer of module enabling!
>>>>
>>>>> do any of you do anything similar? or do you have a different
>>>> system?
>>>>
>>>> I have a Drupal project that periodically needs to get
>>> cloned into
>>>> a new
>>>> instance. I ended up writing a Perl script to handle the
>>> tedious
>>>> parts of
>>>> cloning the database, copying over and resources, erasing the
>>>> un-needed
>>>> content and writing a new settings.php. That's probably a
>>> raunchy
>>>> hack,
>>>> but it was easier (for me) than learning the install profile
>>>> system. It
>>>> does require that you understand Drupal's database schema
>>> very well.
>>>>
>>>>
>>>> It's a slightly different question than what you're asking,
>>> but for
>>>> maintaining Drupal sites with a minimum of hassle I use a
>> method
>>>> largely
>>>> based on David Grant's writeup:
>>>>
>>> <http://www.davidgrant.ca/maintaining_vendor_sources_with_subversion
>>>
>>>>
>>>>
>>>>
>>>> I pretty much do the same thing, but end up doing a bunch of
>>>> configuration by hand. I too was hoping to learn the install
>>> profile
>>>> to create a baseline of modules I want all the time.
>>>>
>>>>
>>>>
>>>> -t
>>>>
>>>> _______________________________________________
>>>> consulting mailing list
>>>> consulting at drupal.org <mailto:consulting at drupal.org>
>>> <mailto:consulting at drupal.org <mailto:consulting at drupal.org>>
>>>> http://lists.drupal.org/mailman/listinfo/consulting
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Christian
>>>>
>>>
>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> consulting mailing list
>>>> consulting at drupal.org <mailto:consulting at drupal.org>
>>>> http://lists.drupal.org/mailman/listinfo/consulting
>>>>
>>>
>>> _______________________________________________
>>> consulting mailing list
>>> consulting at drupal.org <mailto:consulting at drupal.org>
>>> http://lists.drupal.org/mailman/listinfo/consulting
>>>
>>>
>>>
>>>
>>> --
>>> Abraham Williams | http://the.hackerconundrum.com
>>> Web608 | Community Evangelist | http://web608.org
>>> This email is: [ ] blogable [x] ask first [ ] private.
>>> Sent from: Madison Wisconsin United States.
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> consulting mailing list
>>> consulting at drupal.org
>>> http://lists.drupal.org/mailman/listinfo/consulting
>>>
>>
>> _______________________________________________
>> consulting mailing list
>> consulting at drupal.org
>> http://lists.drupal.org/mailman/listinfo/consulting
>>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: http://lists.drupal.org/pipermail/consulting/attachments/20090307/443da168/attachment.htm
>
> ------------------------------
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>
>
> End of consulting Digest, Vol 38, Issue 22
> ******************************************
More information about the consulting
mailing list