Installation DAQ

Here we list issues and errors encountered while trying to install plugins for Fedwiki:

Github references can fail to install active plugins. It is easier and more robust to use npm should your custom package be available as an npm package.

Should you need to install a custom plugin that is not part of the default wiki install just follow the following instructions:

After that try to load the server again. Another way to achieve the same is to edit the package.json directly and use the following:

"wiki-plugin-plugins": "0.0.1", "wiki-plugin-transport": "0.0.5"

then run npm install and load the server. The problem with the approach you tried is that if you use the plugins sources directly, some of the files needed by the wiki client and server are not yet generated, you would need to cd to the plugins folders and run something like grunt build to generate them. This is not needed if you use the published npm packages because those files are already generated and included the in the npm packages.

# When in doubt - restart

A good quick hack for when things go wrong is to remove the offending package with npm uninstall -g <packageName> and start again. For instance with my customised version of wiki I get good results when I mess up with:

npm uninstall -g wiki npm install -g git://github.com/ViralAcademy/wiki.git

# Permission Errors

You can run into permission errors:

git clone git@github.com:github:ViralAcademy/wiki Permission denied (publickey). npm ERR! git clone git@github.com:github:ViralAcademy/wiki fatal: Could not read from remote repository. npm ERR! git clone git@github.com:github:ViralAcademy/wiki npm ERR! git clone git@github.com:github:ViralAcademy/wiki Please make sure you have the correct access rights npm ERR! git clone git@github.com:github:ViralAcademy/wiki and the repository exists.

In which case - you need to check the ssh keys on your server: see help.github.com

https://help.github.com/articles/error-permission-denied-publickey/

The node package manager (npm) has commands that will install plugins and update the package.json at the same time. You can add plugins and decide later if you want to keep them through other updates.

npm prefix cd <prefix>/wiki npm install wiki-plugin-search --save

# Missing Package Errors

You can also run into errors with missing dependencies. I'm not sure (yet) how to fix these - but it would appear that a simple npm install -g <packageName> for the missign deps would fix things?

npm ERR! code 1 david-2:nodeschool BabyBlue$ npm install -g git://github.com/ViralAcademy/wiki.git npm WARN install:cookie ENOENT: no such file or directory, rename '/usr/local/lib/node_modules/wiki/node_modules/express/node_modules/cookie' -> '/usr/local/lib/node_modules/wiki/node_modules/express/node_modules/cookie' npm WARN install:qs ENOENT: no such file or directory, rename '/usr/local/lib/node_modules/wiki/node_modules/express/node_modules/qs' -> '/usr/lo