I've never met it before. Regardless, with the "custom" option, you probably need to follow the foundry specification for the documentation service. I can't a published spec, but your example URLs seem consistent.
You could probably create a Nginx or Apache proxy that could pass the request on to the approprate URLs. It should be a minimal configuration. If you wanted to stay in python land, you could spawn a SimpleHTTPServer <https://docs.python.org/2/library/simplehttpserver.html> to handle the requests. You might also be able to write a handler on the wiki server that handles the Default.html requests. I'm late to the thread. Did you discover anything else in the past couple weeks? On Wed Dec 17 2014 at 3:54:27 AM Ean Carr <[email protected]> wrote: > > 1) Is it possible to change the URL template which Nuke uses? It forces: > > http://www/Default.html#cshid=Foo > > ...but I need: > > http://www/display/2D/2D+Nuke+Plugins+Foo >
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
