Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: Han So <hansolo2218@gmail.com>
To: Han So <Hansolo2218@gmail.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, galene@lists.galene.org
Subject: [Galene] Re: Client/server setup?
Date: Thu, 1 Dec 2022 22:15:14 -0500	[thread overview]
Message-ID: <29B1DAB3-4733-42B3-9F57-E7B7F6752938@gmail.com> (raw)
In-Reply-To: <87999D9F-C8C1-4EFB-AE88-5D776D9D13C2@gmail.com>

Turns out it worked great in editing the endpoint.  Reverse proxy setting in the config only applies to the UI side.  When putting the “backend” on a different server, it didn’t matter that was behind as different reverse proxy since it was only used in the websocket calls.  

Hans

> On Nov 30, 2022, at 10:12 AM, Han So <Hansolo2218@gmail.com> wrote:
> 
> Nice - how would having a reverse proxy affect the below?
> 
> Hans
> 
>> On Nov 24, 2022, at 3:05 PM, Juliusz Chroboczek <jch@irif.fr> wrote:
>> 
>> 
>>> 
>>> Has anyone done client server separation?  Meaning the UI is on
>>> a different server than the server?
>> 
>> Sure.  After the HTML/JS code is downloaded, the client connects to the
>> WebSocket specified in the "endpoint" field of the .status.json file:
>> 
>> $ curl https://galene.org:8443/group/public/.status.json
>> 
>> So you'd simply need to hack the code to provide a URL on a different
>> server:
>> 
>> https://github.com/jech/galene/blob/master/group/group.go#L1223
>> 
>> You'll probably also need to tweak the CORS headers.
>> 
>> -- Juliusz

  reply	other threads:[~2022-12-02 14:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 20:08 [Galene] " Han So
2022-11-24 10:44 ` [Galene] " Jeroen van Veen
2022-11-24 20:05 ` Juliusz Chroboczek
2022-11-30 15:11   ` Han So
2022-12-02  3:15     ` Han So [this message]
2022-12-02 11:38       ` Juliusz Chroboczek

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://lists.galene.org/postorius/lists/galene.lists.galene.org/

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

  git send-email \
    --in-reply-to=29B1DAB3-4733-42B3-9F57-E7B7F6752938@gmail.com \
    --to=hansolo2218@gmail.com \
    --cc=galene@lists.galene.org \
    --cc=jch@irif.fr \
    --subject='[Galene] Re: Client/server setup?' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox