Subj : Re: synchronet behind a reverse proxy
To   : martylake
From : echicken
Date : Sat Nov 27 2021 04:35:00

  Re: Re: synchronet behind a reverse proxy
  By: martylake to echicken on Fri Nov 26 2021 13:54:55

 ma> What is the process to deliver this fix to the docker image ? And how do

When we're satisfied with how it's all set up and testing is done, I'll merge this branch into the main one. Anyone who updates or installs Synchronet afterward will get the changes.

However your docker-based install normally gets updated, that'll take care of it.

(Allow that these changes won't be in nightlies immediately.)

 ma> you manage synchronet's configuration files with regard to upgrading
 ma> synchronet ? The way I did it (modifying the files in ctrl/ and
 ma> overwriting /web from /backups), I feel like I will loose these
 ma> modifications next time I pull, but maybe I am wrong ? 

I don't know enough about how your docker image is set up / updated to say for sure. If it's like this:

http://wiki.synchro.net/install:docker

It's unclear to me whether the stuff listed under "Volumes" is impacted when you update to a newer image.

They single out ctrl/text.dat as something that gets overwritten if there's an updated version; this is generally unnecessary, and is unnecessarily destructive.

Meanwhile I'm not sure what the deal is with the /sbbs/web directory. I get the sense that you're meant to update it manually as you go. (There are probably better ways this could be set up, for webv4 at least.)

Maybe someone more familiar with this setup can chime in. That wiki page needs some building out.

 ma> I have an unrelated issue, should I open a new "thread" for it ? YMODEM-G
 ma> upload with the ftelnet ws works for very small files (<144ko) but does
 ma> not work anymore for bigger files (>174ko). 

 ma> I don't reproduce the issue if I upload files using syncterm.

It's *most likely* a problem with fTelnet, but it's not impossible that both SEXYZ and SyncTERM are doing something wrong in such a way as to be compatible with each other.

I'd start by creating an issue in the fTelnet project on GitHub (if that's where he still hosts it).

You could create an issue on Synchronet's GitLab server as well, but as I said, it's less likely to be a problem on that side.

Short of testing fTelnet with some other software (eg. Mystic) or with Synchronet using a different handler for YMODEM-G (scfg->File Options->Transfer Protocols), I can't think of anything else you can do to narrow it down.
  
---  
echicken   
electronic chicken bbs - bbs.electronicchicken.com
---
 þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.