On Jan 31, 2007, at 3:48 PM, Paul Chvostek wrote:
you just do it manually, perhaps using portdowngrade on each host, or
installing binary packages built on one host?
we build packages on the QA cluster and install them everywhere.
Next, how are people dealing with portaudit info for groups
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hmzz.. currently I manage a bunch of servers - 2-3 machines with 5-6
jails on each running.
I use make package-recursive on one single server and after that
I simply define PACKAGEROOT=http://172.16.4.6/ in the env of the shell.
after that
portupgrade
On Wed, Jan 31, 2007 at 03:48:49PM -0500, Paul Chvostek wrote:
> So ... on the topic of large-scale FreeBSD deployment ...
>
> How are people handling package version consistency in large groups of
> servers? If you have a web farm with 10 hosts, plus 3 hosts in a QA
> farm, and you want to make
On Wed, 31 Jan 2007 15:48:49 -0500 Paul Chvostek wrote:
> How are people handling package version consistency in large groups of
> servers? If you have a web farm with 10 hosts, plus 3 hosts in a QA
> farm, and you want to make sure you're using the same version everywhere
> and upgrading product
On 1/31/07, Paul Chvostek <[EMAIL PROTECTED]> wrote:
So ... on the topic of large-scale FreeBSD deployment ...
How are people handling package version consistency in large groups of
servers? If you have a web farm with 10 hosts, plus 3 hosts in a QA
farm, and you want to make sure you're using
So ... on the topic of large-scale FreeBSD deployment ...
How are people handling package version consistency in large groups of
servers? If you have a web farm with 10 hosts, plus 3 hosts in a QA
farm, and you want to make sure you're using the same version everywhere
and upgrading production to
