@cdb @rdb as much as I’d like to evaluate this very promising plug-in, there’s a big show stopper for our self-hosted installation, so I haven’t even started trying.
Firewall configured to allow traffic on port 6240
(Our) Admins don’t like opening ports left, right and center, for security reasons. That affects me running the server, as well as companies like @Remi ‘s which block certain ports on the client side, possibly though a firewall or a proxy.
Two solutions come to mind:
- I realise that I could still use port 443, but a different subdomain for the seadoc-server. However, I’m not sure whether I would run into cross-domain problems.
- The seadoc server could run under a dedicated path like https://cloud.seatable.com:443/seadoc/. Any edge router like Caddy, Traefik (which we use), or even the internal Nginx of
seatable-servershould be OK with it.- Important question for me: Will the seadoc server work under a non-”/” path?
- I had some success with this in the past: Some software just deal with it, some can be explicitly configured to work under a path, for some systems, I had success with stripping the path on the edge router - and some softwares just crash. Which one is it?
This just repeats the discussion we had with TLDRAW last year here . The problem in this case is not the server component, but the plugin itself. Ever since then, I have been patching the plugin to work with the /tldraw/ sub-path - works like a dream.
Normally, I would just try it and see (and report) what happens, but I don’t have the time at the moment.
