Hi,

My Galene server is running behind a Nginx RP for more than one year. I 
attached my galene server configuration on nginx. It is really simple.

It needs a Let's encrypt certificate, but you may be able to do it with 
ZeroSSL or whatever, or even in basic HTTP with no certs.

I have also a "/room" served from this php code : 
https://github.com/remyd1/galene_room

You can remove this part safely if not needed.

   - edit it and replace galene.example.tld with your FQDN

   - put this in /etc/nginx/sites-available, and do a symlink to it from 
/etc/nginx/sites-enabled

   - test it with "nginx -t"

   - if it is ok, it just should work as is after restarting the nginx 
service.


However, I have a cron job for LE renewals; when certs are changing, you 
may need to check permissions and reload your HTTP server (my server is 
running under a "galene" user, so this user is using acl ({get,set}facl) 
to access to /etc/letsencrypt [1][2]).


Best regards,


[1] in attachments, you can also find a galene.service file to put in 
/etc/systemd/system/, then do "systemctl daemon-reload" (...) "systemctl 
start galene" and an update bash script to update a galene server (my 
galene source code is in /opt/galene-src and galene is installed in 
~galene/...)

[2] To fix permissions after LE renewals, I have this in crontab

@weekly /root/crons/letsencrypt && /root/fix-perms.sh && 
/usr/bin/systemctl restart galene

with fix-perms.sh content :

#!/bin/bash
echo "Checking permissions..."
chown -R galene:galene ~galene
setfacl -R -m u:galene:rx /etc/letsencrypt/
for file in `ls /etc/letsencrypt/live/galene.example.tld/`
do
     setfacl -m u:galene:r /etc/letsencrypt/live/galene.example.tld/$file
done

Le 12/01/2023 à 16:34, Dianne Skoll a écrit :
> On Thu, 12 Jan 2023 16:29:05 +0100
> Juliusz Chroboczek <jch@irif.fr> wrote:
>
>> I think we're agreeing: running Galene in a Docker container is
>> possible, but it's not as convenient as with traditional web apps.  I
>> feel it's not worth the hassle, but reasonable people may disagree.
> If Galene were complicated to set up, that might argue for using
> Docker to reduce installation headaches... but it's a single
> executable with a pretty simple set of config files, so I don't see
> Docker buying much.
>
> Running behind an HTTP proxy, though, is very useful.
>
> Regards,
>
> Dianne.
> _______________________________________________
> Galene mailing list -- galene@lists.galene.org
> To unsubscribe send an email to galene-leave@lists.galene.org

-- 
Chef de projet SI CNRS
Equipe ISI
ISEM UMR5554