-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MWS: 'path-prefix' parameter doesn't work consistently #8759
Comments
Since my original post on the forum, I did follow up on how I think it's currently working. In summary:
Thinking about it some more since making that post, it raises a couple of questions about exactly how the
EDIT to add: After some more thought, I'm reversing opinion on question 2 above. If there's a means to insert a tiddler into the correct bag via command line or other method, then trusting the user to set up the config tiddler for the multiwikiclient is in line with what happens doing the same operation with the regular Node.js server. There just needs to be a documented way for adding that config tiddler without relying on having a working instance that can save from the web browser. |
Thanks @jrbntt
MWS is configured via configuration tiddlers in what we call the "admin wiki", which is an ordinary TW Node.js edition. One of the longer term goals is to be able to use a separate subdomain to access the admin features.
Yes, I think so. The purpose of the path-prefix is to enable people to host MWS other than at the root of a server. MWS should ignore requests that do not start with the path-prefix, and should insert the path-prefix in all the URLs it generates. @webplusai I think the solution in webplusai@a4ee6bc is not quite right; it seems to be redirecting URLs that don't include the path-prefix to include it. |
As reported in the forum, the
path-prefix
parameter to the--mws-listen
command does not work properly.It is intended to allow the server to run with a base path prefix, rather than everything running from the root
/
. See the docs for the same feature with the regular Node.js server.@webplusai would you be able to look at this?
The text was updated successfully, but these errors were encountered: