From owner-freebsd-isp@FreeBSD.ORG Tue Dec 9 13:45:03 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2525A16A4CE for ; Tue, 9 Dec 2003 13:45:02 -0800 (PST) Received: from mx1.heronetwork.com (mail.heronetwork.com [216.254.62.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F28743D09 for ; Tue, 9 Dec 2003 13:45:00 -0800 (PST) (envelope-from swenson@heronetwork.com) Received: by mx1.heronetwork.com (Postfix, from userid 1003) id DE04EA4B85; Tue, 9 Dec 2003 13:44:54 -0800 (PST) Received: from heronetwork.com (ON-01-FW.heronetwork.com [216.254.62.177]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mx1.heronetwork.com (Postfix) with ESMTP id B7390A4B56 for ; Tue, 9 Dec 2003 13:44:53 -0800 (PST) Message-ID: <3FD6425A.7080607@heronetwork.com> Date: Tue, 09 Dec 2003 13:44:58 -0800 From: Scottie Swenson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Freebsd isp isp References: <042601c3be94$c2ff3bd0$019c9752@xp> In-Reply-To: <042601c3be94$c2ff3bd0$019c9752@xp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on nott.heronetwork.com X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.60 Subject: Re: Who are using FreeBSD for Hosting Env. and Which Update Method X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2003 21:45:03 -0000 Greetings, Vahric MUHTARYAN wrote: > I want to know Are anybody usingFreeBSD for their Web Hosting ( PHP + > MYSQL + POSTGRE + APACHE ) Env. or Mail Hosting Env. I'm asking because I > wonder Which Update method are you using ? We have: 1) a "build server" which mirrors the installation images for our server sets. 2) a "source server" which keeps the ports tree up to date (cvsup, etc.) and is NSF mountable to the "build server" and each hosting server. 3) We use the "build server" to build new packages for our environment using portupgrade with the '-p' option to create custom binary packages. 4) Then we have a script which can mount the ports tree, run portupgrade with '-a -PP' options. The -PP keeps things from updating we don't want updated yet. Hence we control what updates when. We are looking to automate the process using cfengine or similar product. This method lets us have a test suite on the build server where we can back off if needed while keeping things up to date. Cheers, Scottie