From owner-freebsd-questions@FreeBSD.ORG Wed Sep 17 10:52:06 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 64308A22 for ; Wed, 17 Sep 2014 10:52:06 +0000 (UTC) Received: from blue.qeng-ho.org (blue.qeng-ho.org [217.155.128.241]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D461AC88 for ; Wed, 17 Sep 2014 10:52:05 +0000 (UTC) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by fileserver.home.qeng-ho.org (8.14.7/8.14.5) with ESMTP id s8HAq16D029150; Wed, 17 Sep 2014 11:52:02 +0100 (BST) (envelope-from freebsd@qeng-ho.org) Message-ID: <541967D1.90108@qeng-ho.org> Date: Wed, 17 Sep 2014 11:52:01 +0100 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Matthias Apitz , freebsd-questions@freebsd.org Subject: Re: A lot of pkg problems References: <2509308.9rytrV7MvD@penguin> <5411A89B.4010707@gmail.com> <1812950.bWcWxrzvJI@penguin> <54189CD1.7070102@webrz.net> <5418A5EE.1030304@hiwaay.net> <541936C5.3080601@qeng-ho.org> <20140917085023.GA1534@tiny-r269739> In-Reply-To: <20140917085023.GA1534@tiny-r269739> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 10:52:06 -0000 On 17/09/2014 09:50, Matthias Apitz wrote: > El día Wednesday, September 17, 2014 a las 08:22:45AM +0100, Arthur Chance escribió: > >> >> Using poudriere to build your own repo is *very* easy and lets you build >> only the packages you need (so is quicker than waiting the four-ish days >> that the main repository takes to build everything), with the options >> you want. > > I can ACK this. I started in August with poudriere and pkg (before I was > used to use the ports tree directly to creat some 1200 pkg_* packages > for my farm of laptops/netbook. > > Ones you have the pieces together and the poudriere server setup, all is > very easy and works as it should. > > The only thing I could not manage until now, was setting up a webserver > to monitor the progress of the running poudriere jail. Do you have a > small howto for this? I have nginx installed in the host, but can not > get the dynamic movie into the browser firefox. It's probably not the most elegant way of working, but this works for me. In my nginx.conf the poudriere related bits are location /pkgs/ { alias /usr/local/poudriere/data/packages/; autoindex on; autoindex_exact_size off; autoindex_localtime on; } location /logs/ { alias /usr/local/poudriere/data/logs/; index index.html; autoindex on; autoindex_exact_size off; autoindex_localtime on; default_type text/html; types { text/plain log; } } That's with poudriere's BASEFS=/usr/local/poudriere My repo URL is http://${HOST}/pkgs/${JAIL}-default and my URL for monitoring the build is http://${HOST}/logs/bulk/${JAIL}-default/latest/index.html where ${JAIL} is the poudriere jail I'm using. If you use -z SET for different options, replace "default" with ${SET}. You might want to add URL_BASE=file://${BASEFS}/data/logs or URL_BASE=http://${HOST}${BASEFS}/data/logs to your poudriere.conf as well, so it can give you helpful pointers on the build machine. Note there's no slash before ${BASEFS} in those URLs as it begins with one already.