Skip to content

Commit

Permalink
Installing as a gem is the canonical way to install the plugin
Browse files Browse the repository at this point in the history
Delivering Redmine plugins as gems comes with too many benefits to ignore:
http://mentalized.net/journal/2015/05/16/redmine-plugins-should-be-gems/
  • Loading branch information
koppen committed May 30, 2015
1 parent 3da1be8 commit 4f3e919
Showing 1 changed file with 0 additions and 11 deletions.
11 changes: 0 additions & 11 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,22 +15,11 @@ That approach works perfectly fine, but is a bit heavy-handed and cumbersome. Th

### 1. Install the plugin

You have two options for installing the plugin:

#### A: As a RubyGem

1. Add the gem to your Gemfile.local:
`gem "redmine_github_hook"`
2. `bundle`
3. Restart your Redmine

#### B: As a plugin

1. Follow the plugin installation procedure outlined in the [Redmine wiki](http://www.redmine.org/wiki/redmine/Plugins).
* Make sure that Redmine GitHub Hook is installed in a directory named `redmine_github_hook`
* Easiest way: change in your plugins directory and pull with git: `git clone git://github.com/koppen/redmine_github_hook.git`
2. Restart your Redmine.

### 2. Add the repository to Redmine

Adding a Git repository to a project (note, this should work whether you want to use Redmine GitHub Hook or not).
Expand Down

0 comments on commit 4f3e919

Please sign in to comment.