 |
That manual page in the online manual: http://www.mantisbt.org/manual/manual.troubleshooting.installation.php "www.example.com" is meant to be taken as an example. You are meant to replace that with wherever your Mantis installation is actually located. That's also why it's not a hyperlink that you can click. For consistency with the install guide (Details for New Installations of v1.0.0a2 or later, step 3)... http://www.mantisbt.org/manual/manual.installation.php ...we should replace "www.example.com" with "yoursite" |
 |
I guess I understand but you guys are too 'in the project' with the doc. Who is the manual for, especially the local one? Me while I set up mantis or my developers when using mantis, you guys when doing bugs on Mantis... When I look at the Mantis what is that very unhelpful even if it was on my site frustrated... |
|
|
Honestly, I didn't know there was a downloadable copy of the manual. I've only ever used the online manual on the mantisbt.org web site. Who's the manual for? I would say it's for the administrator setting up your local Mantis, and for the people who use Mantis. Who's the local version for? Probably for people who would like to be able to read it while not connected to the Internet -- perhaps someone who has a copy of Mantis installed on a laptop. Or for people who have a good local network but a slow and/or expensive link to the Internet. Only you can know where you installed Mantis on your own server. Did you install it at http://bugs.somebigcompany.com ? or http://www.mydomain.com/tracker ? or http://localhost/~dhrowe/test/mantisbt ? Only you know where you've put it. |
 |
Ideally, I would like to have an Administrator Guide and a User Guide. The administrator guide is mainly for setting up Mantis. The user guide should be to day to day operations. |
 |
With regards to the intended audience for the Admin guide, it clearly states at the beginning: This book is targeted at MantisBT administrators, and documents the installation, upgrade, configuration, customization and administration tasks required to operate the software. As for changing 'example.com' to something else, as pointed out by ryandesign, this is simply not feasible. I'm resolving this as no change required. |
- Anonymous
