Subj : Re: Anybody ever try installing Synchronet on a prebuilt NAS viaDocker?
To   : Waethorn
From : Tracker1
Date : Wed Sep 21 2022 21:34:09

On 9/14/22 17:34, Waethorn wrote:
 > I just was playing around with the Docker options on a Synology NAS
 > (an x86 model - a DS720+) and trying to get Synchronet installed on
 > it.

Should be able to use the bbs-io images without issue (assuming it's an 
x86 model) otherwise, you'd have to do your own build.

 > Seems that there's a whole whackload of common service ports that are
 > reserved in Synology's DSM NAS OS that require a lot of workarounds,

You *should* be able to run all the BBS services with redirects from 
non-standard ports...

ex: router:23 -> nas:50080 -> docker-instance:80

 > even when you're not using those services on the NAS.  I'm just
 > wondering if anyone has any experience with that kind of deployment
 > and what kind of problems you ran into

Not many... worth noting, that if your ISP blocks common service ports, 
most do for residential connections... you'll need to accept incoming on 
those non-standard ports.  Also, won't be able to use the secure certs 
via Let's Encrypt as it is... I hadn't looked into it enough to try to 
import the certs from a different system that used DNS to do the let's 
encrypt.

 > and the conclusions you got to at the end of it all.  I didn't spend
 > a whole lot of time on it, but I did try rerouting some of the web
 > ports, although I ended up getting the built-in nginx web server
 > giving remote application errors.  I just found that using a full VM
 > is a whole lot easier.

Yeah, the default web ports are *DEFINITELY* captured by the NAS box... 
mine does have the option to reverse-proxy certain hostnames though, you 
might consider that.

 > Anyway, if anybody has any tips from their own experience, I'd welcome
 > them, otherwise I'll just continue on with the VM that I'm working
 > with.

Not much more than mentioned above... the main thing would be listening 
on non-standard ports, and having your router NAT the inbound to the 
listening ports.

You also may want to look at Caddy as a reverse-web proxy if you want to 
have more sites running that aren't synchronet for web usage... NginX 
works too, just caddy is slightly easier imo.
-- 
Michael J. Ryan - tracker1@roughneckbbs.com
---
 þ Synchronet þ Roughneck BBS - roughneckbbs.com

.