From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] daily kan-ban update 09jun2020
Date: Tue, 9 Jun 2020 23:48:24 +0100
Message-ID: <CAPweEDwjz=N0ga9iAc4utqZw3J8yhN54fyTscpnyTbk4qn9zmw@mail.gmail.com> (raw)
In-Reply-To: <20200609214936.GH14030@phcomp.co.uk>
On Tue, Jun 9, 2020 at 10:49 PM Alain D D Williams <addw@phcomp.co.uk> wrote:
>
> Sigh ... trying to get bzkanban working ......
>
> I implemented the latest bugzilla - this works nicely (bugzilla that is, not bzkanban)
>
> If you want to play with it you need to put this into your /etc/hosts
>
> 46.235.227.77 bugs-5.0.6.libre-soc.org
nicely done, alain. actually we can probably put that into the dns.
>
> I can make that the current bugzilla if it does not break anything.
>
>
> So: I then got bugzilla (5.0.6) working under another Debian 10 machine under
> nginx with postgresql - that works.
>
> Blood on my keyboard when I tried to get bzkanban working.
>
> Run up Apache and, after a couple of sillies, it works - bugzilla and bzkanban I mean.
hurrah!
> Flip back & forth between the two - never under works nginx, always under
> apache. I'm stopping - there is an Einstein quote popping up in my head.
:)
>
> So: if you want bzkanban - I can install apache & replace nginx. I'm *****ed
> if I can see another way.
>
> Is there a good reason for needing nginx ?
mmm... i switched all my web services (including for clients) over to
it after learning of its lower workload and greater security by
design.
if it's getting in the way, although it makes me slightly nervous we
can flip over to it.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 21:49 Alain D D Williams
2020-06-09 22:48 ` Luke Kenneth Casson Leighton [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-09 13:11 Luke Kenneth Casson Leighton
2020-06-09 13:23 ` Tobias Platen
2020-06-09 16:20 ` Luke Kenneth Casson Leighton
2020-06-09 17:21 ` Jacob Lifshay
2020-06-09 17:44 ` Luke Kenneth Casson Leighton
2020-06-09 19:35 ` Cole Poirier
2020-06-09 20:15 ` Luke Kenneth Casson Leighton
2020-06-09 21:01 ` Cole Poirier
2020-06-09 21:48 ` Luke Kenneth Casson Leighton
2020-06-09 22:07 ` Luke Kenneth Casson Leighton
2020-06-10 0:38 ` Cole Poirier
2020-06-10 13:16 ` Luke Kenneth Casson Leighton
2020-06-10 18:53 ` Michael Nolan
2020-06-10 21:30 ` Cole Poirier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPweEDwjz=N0ga9iAc4utqZw3J8yhN54fyTscpnyTbk4qn9zmw@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git