As far as I see, wikijs can only be hosted at domain root (http://wiki.example.com/). Would be cool if it could also be hosted at a subpath, like http://example.com/wiki/
There's no plan to allow for subfolder installations. Use a subdomain instead.
@Nicolas Giard: any reason for that? It might be a blocker for those who need it..
@Lars Solberg: Because it adds unnecessary complexity to the app. From path parsing, path permissions, links within content that must be rewritten + again if the subfolder changes, all assets must be prefixed, potential cookie collision with other apps to the sheer amount of extra github support tickets because of incorrect configuration in Wiki.js or their reverse-proxy.
Most support tickets for v1 were concerning the site url not being setup correctly, which would necessary for subfolder install. Something I'd rather not repeat with v2.
Unless someone can give me a really compelling reason against using subdomains, sub-folder installation will not be implemented for the foreseeable future.
@Nicolas Giard: I understand what are the problems. In my case I am already using a third level domain to host the application and I cannot add a fourth level domain or add another third level domain because due to my provider they are not free. Now I have to switch to another wiki platform (sadly).
@Nicolas Giard: I have no choice in the domain:port selection at my company, and really want to use Wiki.js but can't until this functionality exists. Most features are nice to have, but this is a deal breaker for Wiki.js adoption at my company.
I realize this is an old thread, but I thought I'd share the steps I needed to take in order to implement a subdomain approach for our wiki-in-an-iframe proof of concept:
* request subdomain on internal intranet, obtain certs etc. for wiki.xxxxx.com
* relax Content-Security-Policy frame-src meta on all calling pages to include wiki.xxxxx.com
I think the subfolder idea has some merit.
Thanks for a great product.