cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Koberg" <>
Subject RE: machine name for
Date Mon, 04 Nov 2002 11:23:13 GMT

> -----Original Message-----
> From: Tom Klaasen []
> Sent: Monday, November 04, 2002 2:56 AM
> To:
> Subject: Re: machine name for
> >7) chyrsalis
> >The hard-shelled pupa of a moth or butterfly.
> This collides with krysalis (
> Krysalis is not an official ASF project, but they're very cocoon-related.
> Moreover, the goal of krysalis is to develop cocoon-based
> applications, and chrysalis would then showcase those applications...
> I think it takes less to confuse a user.
> btw:
> 8) butterflies
> When using cocoon, you can get beautiful butterflies :-)
> The applications are the end-point of cocoon development, not their
> starting point (like "pupa" etc would suggest)

I just saw an ad yesterday during the 49ers v. Raiders game that had shown these
mysterious cocoons showing up all over. Then, what pops out? The microsoft MSN

But why does the machine name need to be changed if it is going to be a bunch of
virtual hosts pointed from the domain?

I would suggest somoething like the following for all projects: -- for development purposes

Then when ready to go to QA, create a branch/tag and promote the site to:

If something is broken, fix it in the branch and keep QAing until it can be
promoted to something like:

>From the 'certified' stage the project can break out of it's cocoon and take
flight (by being copied over to a live stage/server).


> tomK
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, email:

To unsubscribe, e-mail:
For additional commands, email:

View raw message