Skip to content

Commit 4f3e919

Browse files
committed
Installing as a gem is the canonical way to install the plugin
Delivering Redmine plugins as gems comes with too many benefits to ignore: http://mentalized.net/journal/2015/05/16/redmine-plugins-should-be-gems/
1 parent 3da1be8 commit 4f3e919

File tree

1 file changed

+0
-11
lines changed

1 file changed

+0
-11
lines changed

README.md

Lines changed: 0 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -15,22 +15,11 @@ That approach works perfectly fine, but is a bit heavy-handed and cumbersome. Th
1515

1616
### 1. Install the plugin
1717

18-
You have two options for installing the plugin:
19-
20-
#### A: As a RubyGem
21-
2218
1. Add the gem to your Gemfile.local:
2319
`gem "redmine_github_hook"`
2420
2. `bundle`
2521
3. Restart your Redmine
2622

27-
#### B: As a plugin
28-
29-
1. Follow the plugin installation procedure outlined in the [Redmine wiki](http://www.redmine.org/wiki/redmine/Plugins).
30-
* Make sure that Redmine GitHub Hook is installed in a directory named `redmine_github_hook`
31-
* Easiest way: change in your plugins directory and pull with git: `git clone git://github.com/koppen/redmine_github_hook.git`
32-
2. Restart your Redmine.
33-
3423
### 2. Add the repository to Redmine
3524

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

0 commit comments

Comments
 (0)