From directory-dev-return-3686-apmail-incubator-directory-dev-archive=incubator.apache.org@incubator.apache.org Mon Jan 10 21:38:35 2005 Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 77014 invoked from network); 10 Jan 2005 21:38:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Jan 2005 21:38:35 -0000 Received: (qmail 98916 invoked by uid 500); 10 Jan 2005 21:38:35 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 98873 invoked by uid 500); 10 Jan 2005 21:38:34 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 98860 invoked by uid 99); 10 Jan 2005 21:38:34 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=FROM_ENDS_IN_NUMS,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of aok123@bellsouth.net designates 205.152.59.66 as permitted sender) Received: from imf18aec.mail.bellsouth.net (HELO imf18aec.mail.bellsouth.net) (205.152.59.66) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 10 Jan 2005 13:38:34 -0800 Received: from [172.16.1.8] ([65.80.200.112]) by imf18aec.mail.bellsouth.net (InterMail vM.5.01.06.11 201-253-122-130-111-20040605) with ESMTP id <20050110213832.PJFI2042.imf18aec.mail.bellsouth.net@[172.16.1.8]> for ; Mon, 10 Jan 2005 16:38:32 -0500 Message-ID: <41E2F5C0.8090106@bellsouth.net> Date: Mon, 10 Jan 2005 16:38:08 -0500 From: Alex Karasulu User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Apache Directory Developers List Subject: [site] building and deploying part II Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi, WARNING: I have not yet tried Brett's plugin changes just yet. This is the next thing I will be doing. As promised here's part II. First off you know you can build the sitedocs using either one of these commands with Maven ... 1). maven mutliproject site:deploy (for projects with many subprojects) 2). maven site:deploy These commands deploy generated sitedocs to the staging area which is currently in my home directory here: http://www.apache.org/~akarasulu/rsynced-sites/directory This is password protected along with the page used to deploy sites to their target docroot. This is primarily to prevent bots from causing problems. You can get the username password by cating the following file in my home directory. All ASF committers should be able to access my home directory and read this file: ~akarasulu/deployer-userpasswd.txt Here's the page to hit to deploy the site: http://www.apache.org/~akarasulu/rsynced-sites This is protected using the same username password. Once you get in just hit the deploy button. It should rsync the changes you have made to files in the staging area to the docroot of your project. I think using Brett's modified plugin will be a much better approach to managing staged publication. I'll play with the plugin now and report back soon. Also turns it out that Dave Crossley is working on a publication server/service area where we can stage our sitedocs. So we might be able to get that staging area sooner than we thought. Cheers, Alex