Thanks Mike and Mike.
Is there a reason why these extra http requirements couldn't be in the
http/conf.d/kojiweb.conf by default. It would seem like everybody
would have to end up adding them.
This build system really does work so much better with an additional host.
Maybe my builds really weren't serialized by repo tasks, but the repo
tasks workload were causing build tasks to wait.
Doug
On Fri, Mar 5, 2010 at 11:30 AM, Mike McLean <mikem(a)redhat.com> wrote:
On 03/05/2010 11:14 AM, Doug Reiland wrote:
> ok, I saw some old discussion of kojid's topurl setting instead of topdir
>
> After playing with this a bit, I think it is working.
>
> Let me first ask, what should topurl be set to?
topurl should be a url that serves the content of /mnt/koji
pkgurl should be a url that serves the content of /mnt/koji/packages
> So far, I have had to setup aliases in httpd/conf.d/kojiweb.conf for
> the following:
>
> Alias /packages/ /mnt/koji/packages/
> Alias /remote-koji/ /mnt/koji/
>
> In my remote builder, I have:
>
> topurl=http://<server_name>/remote-koji
> server=http://<sever_name>/kojihub
> pkgurl=http://<server_name>/packages
>
> Am I doing this correct?
This should work, though it seems a little silly to me to create the
separate alias for packages when you could just use
http://<server_name>/remote-koji/packages
--
buildsys mailing list
buildsys(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/buildsys