# Basics on Installing a plugin **URL:** \ **Category:** rubyonrails-talk\ **Created:** [November 30, 2007, 11:23pm UTC](https://discuss.rubyonrails.org/t/basics-on-installing-a-plugin/21083 "2007-11-30T23:23:57Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![HiddenBek](https://avatars.discourse-cdn.com/v4/letter/h/bc79bd/32.png) [@HiddenBek](https://discuss.rubyonrails.org/u/HiddenBek)\ **Post date:** [November 30, 2007, 11:23pm UTC](https://discuss.rubyonrails.org/t/basics-on-installing-a-plugin/21083/1 "2007-11-30T23:23:57Z")
Subversion is a version control system. It allows you to track the history of your source code and makes collaboration much easier, since people can submit changes, get updates, and resolve conflicts regardless of their physical location. Version control is an invaluable tool in a programmer's toolbox and is definitely something you should learn more about. [http://svnbook.red-bean.com](http://svnbook.red-bean.com) is an excellent reference. You only need to read the first couple of chapters to get a handle on the basics. Many rails plugins do require subversion to install, but this one doesn't. If the URL begins with svn://, then subversion is required. You should run script/plugin from the root of the directory that was generated by the rails command, not in the app directory. That is, when you type ls or dir (depending on your operating system), you should see app, config, lib, log, and so forth. If, after running the plugin command, you get something like "ruby: No such file or directory -- script/plugin (LoadError)", then you're in the wrong place. The command you tried should work if you're running it from the correct place. If it doesn't, I suspect there's probably a network issue of some sort. Are you behind a proxy? Give us the exact error message and someone can probably help you. ---
**Author:** ![HiddenBek](https://avatars.discourse-cdn.com/v4/letter/h/bc79bd/32.png) [@HiddenBek](https://discuss.rubyonrails.org/u/HiddenBek)\ **Post date:** [December 1, 2007, 1:59am UTC](https://discuss.rubyonrails.org/t/basics-on-installing-a-plugin/21083/2 "2007-12-01T01:59:46Z")
Just because it thinks the plugin is installed doesn't necessarily mean it installed correctly the first time. Rails won't attempt a reinstall if the directory for that plugin already exists, even if the previous install failed halfway through. I would suggest adding -- force to the end of the command to force a reinstall, just to be sure. If you don't get an error, you should be good to go. ---
**Author:** ![HiddenBek](https://avatars.discourse-cdn.com/v4/letter/h/bc79bd/32.png) [@HiddenBek](https://discuss.rubyonrails.org/u/HiddenBek)\ **Post date:** [December 1, 2007, 2:12am UTC](https://discuss.rubyonrails.org/t/basics-on-installing-a-plugin/21083/3 "2007-12-01T02:12:53Z")
The plugin will install into the vendor/plugins directory. ---
**Author:** ![HiddenBek](https://avatars.discourse-cdn.com/v4/letter/h/bc79bd/32.png) [@HiddenBek](https://discuss.rubyonrails.org/u/HiddenBek)\ **Post date:** [December 1, 2007, 3:21am UTC](https://discuss.rubyonrails.org/t/basics-on-installing-a-plugin/21083/4 "2007-12-01T03:21:53Z")
> hoot! Glad to hear it. I believe "w00t!" is technically the correct term 🙂