unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Lassieur" <clement@lassieur.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 32233-done@debbugs.gnu.org
Subject: bug#32233: Cuirass: Berlin web API times out
Date: Mon, 23 Jul 2018 17:29:16 +0200	[thread overview]
Message-ID: <87sh4at1gz.fsf@lassieur.org> (raw)
In-Reply-To: <87h8kqovgg.fsf@gnu.org>

Ludovic Courtès <ludo@gnu.org> writes:

> Clément Lassieur <clement@lassieur.org> skribis:
>
>>> Is the Web UI already in the current ‘cuirass’ package?
>>
>> Soon!  But I think we should change the NGINX config nonetheless because
>> the json API is useful.
>
> The JSON API is available; see ‘berlin-locations.conf’.
>
>>> If so, what do we need to change in the nginx config?
>>
>> I guess we could add:
>>
>> server {
>
> [...]
>
>>     location / {
>>         proxy_pass http://localhost:8081;
>>     }
>> }
>
> I think this change should go do ‘berlin-locations.conf’.

That would conflict with the '/' location of ports 80 and 443.  I was
rather thinking about using port 8081 for Cuirass.  In that case the
'server' block would be needed in berlin.conf.  We would also remove

    # Cuirass.
    location /specifications { proxy_pass http://localhost:8081; }
    location /jobsets { proxy_pass http://localhost:8081; }
    location /build { proxy_pass http://localhost:8081; }
    location /api { proxy_pass http://localhost:8081; }

from berlin-locations.conf.

Otherwise we need to think about what routes go to Cuirass and what
routes go to Guix publish.  Alternatively, we could use another domain
name with ports 80 and 443, but it's more work.

WDYT?

  reply	other threads:[~2018-07-23 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-21  9:29 bug#32233: Cuirass: Berlin web API times out Clément Lassieur
2018-07-23  9:08 ` Ludovic Courtès
2018-07-23 11:54   ` Clément Lassieur
2018-07-23 14:52     ` Ludovic Courtès
2018-07-23 15:29       ` Clément Lassieur [this message]
2018-07-23 20:07         ` Ludovic Courtès
2018-07-23 20:12           ` Clément Lassieur
2018-07-29 23:25             ` Clément Lassieur

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sh4at1gz.fsf@lassieur.org \
    --to=clement@lassieur.org \
    --cc=32233-done@debbugs.gnu.org \
    --cc=ludo@gnu.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).