Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 93689 invoked from network); 30 Aug 2003 12:22:56 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 30 Aug 2003 12:22:56 -0000 Received: (qmail 20248 invoked by uid 500); 30 Aug 2003 12:22:46 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 20164 invoked by uid 500); 30 Aug 2003 12:22:45 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 20127 invoked from network); 30 Aug 2003 12:22:44 -0000 Received: from unknown (HELO host.leverageweb.com) (64.91.232.157) by daedalus.apache.org with SMTP; 30 Aug 2003 12:22:44 -0000 Received: from va-leesburg-cmts5c-90.chvlva.adelphia.net ([67.21.159.90] helo=leverageweb.com) by host.leverageweb.com with asmtp (Exim 3.36 #1) id 19t4hs-00047k-00 for dev@cocoon.apache.org; Sat, 30 Aug 2003 08:19:52 -0400 Message-ID: <3F509D20.3020306@leverageweb.com> Date: Sat, 30 Aug 2003 08:48:32 -0400 From: Geoff Howard User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [RT] Implementing Cocoon Blocks References: <3F4F728F.2050203@verizon.net> <3F4F7C20.9060709@leverageweb.com> <3F4F7EE7.2010604@verizon.net> <3F501293.4030502@leverageweb.com> <3F500E64.7040700@isisnetworks.net> In-Reply-To: <3F500E64.7040700@isisnetworks.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - host.leverageweb.com X-AntiAbuse: Original Domain - cocoon.apache.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [0 0] X-AntiAbuse: Sender Address Domain - leverageweb.com X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Ryan Hoegg wrote: > This seems to be blurring the lines between the responsibilities of > Cocoon and the container. We might be able to reuse some ideas or even > code that has been done in Merlin, Fortress, Loom, or Plexus for > deployment time configuration and dependencies. Anyone familiar with Fortress (which it seems we're going to as an intermediate until Merlin's full release) know if there's something which can help? Berin? Geoff > Geoff Howard wrote: > >> Also, how to recreate the deploy step efficiently? For example: >> >> You deploy a block with some dependencies and configuration. The >> block deploy process walks you through setting configs and resolving >> dependencies. You then have no record of these deployment choices >> except in wiring.xml which is not meant for human consumption. >> Perhaps it would be good to record these human-step deployment time >> configurations in a conf file which could be easily reprocessed to >> easily re-deploy all blocks to their last configuration. >> >> Alternate versions of this file may be needed as blocks move from dev >> to staging to live, etc.