I modified the title to assist.
1 Like
If I could configure, per “recipe,” a password for basic authentication, using HTTP basic auth, just like in the Node.js version where we have the parameter -listen username=<user> password=<pass>.
It would also be interesting if I could configure, per “recipe,” basic authentication for TW, similar to the Node.js version where we have the parameter --password <pass>.
They’re small details, but they help build a slightly more secure environment.
Don’t know if this has been covered, but I’d love a UI to sort tiddlers into different bags, perhaps which use filters to allow me to sort/retrieve tiddlers.
2 Likes
Furthermore… It would be very useful to have the ability to configure a base path, as well as a custom path for recipes.
By default, MWS is accessed via IP, for example:
https://127.0.0.1/
And recipes are accessed at:
https://127.0.0.1/wiki/<recipe_name>
It would be helpful to allow passing a base path via the command line. For instance, something like:
npx mws listen --listener port=8081 host="127.0.0.1" secure=true path="MWS"
This would make the MWS admin panel accessible at:
https://127.0.0.1/MWS/
Additionally, it would be useful to configure the recipes route from within the MWS admin panel. In that case, recipes could be accessed like:
https://127.0.0.1/MWS/<recipe_name>
or even:
https://127.0.0.1/MWS/<custom_prefix>/<recipe_name>
This would provide more flexibility when running MWS behind a reverse proxy or under a subpath.
Your path suggestion is something that I’ve already built into the internal code. It just isn’t very accessible to configure yet. I still have to work on that part.
The suggestion about basic auth: I think we’re moving to cookie-based auth with access controls, so that’s very similar to what you’re requesting, but slightly more secure.
It would be great to have the possibility to sync with @BurningTreeC’s TiddlyDesktop… and to use it as frontend to configure the server.