In regards to Doku:
I suspect, on the surface, part of it is hardware. It is a wiki, so it is just serving up text and pictures, so I don't understand why the plug has a hard time. It is not slow everywhere, but certain things take a long time. I suspect unnecessary overhead, or timing out while doing things that the tonido PHP environment doesn't support. I am not sure yet though.

In regards to PM:
Yeah, the license is what makes it attractive and easy for me to distribute. The cookbook recipes are pretty good. Most work great. I have like 20 different ones running on my personal wiki and I don't really see much of a performance hit. Now that I am familiar with the structure of the cookbook recipes, I have modded a bunch and even contributed to some.

That would be my guess too.

I am trying to install and use. All my wiki pages are being generated with http://192.168.x.x:10001 links. Is there something I need to do to make these my domain instead? The pages won't work outside my network.

I learned this by accident the other day. If you're using their relay service, go to [your profile name].tonidoid.com/dyn/pmwiki/index.php.

Works for me anyway...

After I get Tonido Shell to the Tonido Market, I am going to revisit this PmWiki plugin.

Originally I was having the opposite problem where I couldn't get the wiki to format URLs properly inside my network. I am currently asking PHP to give me the the HOST and the PORT. On most servers, I think that is sufficient, but it appears that their is something quirky about what you are getting with the Tonido Relay. I may be able to come up with an alternative solution to format the URLs proberly; there are a number of ways to do this.

Also, I plan on modifying the the wrapper that installs/launches the wiki because it is gobbling up to much load time; it takes longest to load the wrapper than anything else. I think I know what the problem is, I just need to do some tests.

edit: Corrected incorrect assumption

I guess I don't know enough about this but when I go to /dyn/pmwiki/ is it bypassing any Tonido security? Also, I haven't really noticed a performance issue when accessing PmWiki externally.

Easy enough to check. Close your browser completely, open the /dyn/pmwiki URL and see if you can access it.
If yes, the permission is not set and that can be changed by a simple manifest.xml file.

If not, you will need to login into your tonido account before attempting to open the wiki and then it will work. So you are secure.

There should not be a performance issue loading externally. I prefer to load the wiki externally from the Tonido UI.

The only performance issue that exists is my overhead for determining whether or not the wiki needs to be installed. It takes around 3seconds with the way I am doing it. I need to shorten this and be smarter about what I am doing.

You do not need to be logged into Tonido to access the wiki, but if you prefer to be behind Tonido Authentication, you can modify the manifest.xml as stated by Madhan.

URL issue is separate form the above stated items. It is related to what is returned as the HOST and PORT via the $_SERVER['HOST'] and $_SERVER['PORT'] while under the Embedded Tonido UI while using your own redirect service.

Gotcha. Thank you both for the information. I will update that manifest.xml file since I am able to access the wiki using /dyn/pmwiki/. Is that default behavior after installing an application in Tonido or did I miss something when installing PmWiki or PHP?

You can always access the Wiki from dyn/pmwiki regardless of being behind Tonido Authentication or not. But if you change the authentication to require Tonido Login, you first must login into Tonido, then it will be accessible via Tonido Embedded UI or dyn/pmwiki.

Currently, the PmWiki plugin does not require Authentication of any kind from Tonido; it has its own authentication. I did this because, currently, you can not access PmWiki directly if you are a guest from the guest home page. So I figured, why make family and friends login into Tonido and then enter a separate url and enter another password. So I just serve it up with only PmWiki Authentication. But note, the Tonido Authentication requirement has nothing to do with if PmWiki can be accessible via dyn/pmwiki, it just affects if you can access pmwiki period.