Closed elijah closed 6 years ago
I think you might need to modify app.js
for that. FILEBOT_NODE_CLIENT
is the server-side path to the web app files. You want PUBLIC_HTML
to be /
which doesn't seem to be configurable right now.
I will probably try it tonight and let you know :)
On Nov 26, 2017 16:31, "Reinhard Pointner" notifications@github.com wrote:
Setting export FILEBOT_NODE_CLIENT / in the launcher should work. Not tested though.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/filebot/filebot-node/issues/20#issuecomment-347044070, or mute the thread https://github.com/notifications/unsubscribe-auth/AACok2PyBsjv4UrnBvWBxy5VGynffbrXks5s6ebJgaJpZM4Qq33r .
Hi there - I'd like to reroot filebot-node so that I can run it on the root of a domain rather than under the /filebot/ pathing. Yes, yes, I could set up a reverse proxy to remap all of this, but there are various reasons that I'd prefer not to mess with it.
Am I reading correctly that the logic is that such that I could use a FILEBOT_NODE_CLIENT set to / rather than /filebot/ to get this to happen? I'm reading around in server-nodejs/app.js -- it looks like that trickles down and the PUBLIC_HTML vars get built out of it.