otrs_connector 0.5.1 → 0.5.2
Sign up to get free protection for your applications and to get access to all the features.
- data/README.rdoc +19 -1
- data/VERSION +1 -1
- data/lib/otrs.rb +2 -2
- data/otrs_connector.gemspec +1 -1
- metadata +2 -2
data/README.rdoc
CHANGED
@@ -4,12 +4,30 @@ otrs_connector connects to the OTRS API, wich some modifications that opens up m
|
|
4
4
|
By default only the ticketing system is opened to the external API in OTRS.
|
5
5
|
Please see my other github project, rails_otrs to download the latest OTRS modifictions so that this will work correctly.
|
6
6
|
|
7
|
+
otrs_connector only supports OTRS 3.0.x
|
8
|
+
Support for 3.1.x is coming but is a major refactor (on both the OTRS API interface, which needs to be re-written and the main connector here).
|
7
9
|
|
8
|
-
|
10
|
+
|
11
|
+
This gem makes extensive use of ActiveModel and ActiveSupport (json encoding/decoding).
|
12
|
+
It is tested with both Rails 3.0.x and Rails 3.1.x and should work with 3.2.x
|
13
|
+
|
14
|
+
===How to install
|
9
15
|
gem install otrs_connector
|
10
16
|
or Add to your gemfile:
|
11
17
|
gem 'otrs_connector'
|
12
18
|
|
19
|
+
|
20
|
+
===Configuration Options
|
21
|
+
Put these in your environment configuration, change based on your setup:
|
22
|
+
OTRS.user = 'rails'
|
23
|
+
OTRS.password = 'rails'
|
24
|
+
OTRS.api_url = 'http://localhost/otrs/json.pl'
|
25
|
+
|
26
|
+
The username/password should be setup as agents in your OTRS setup.
|
27
|
+
Make sure the agent has proper permissions to access what you need from the API.
|
28
|
+
The API url is the custom API interface file described above. This will change once 3.1 support is added
|
29
|
+
|
30
|
+
|
13
31
|
== Contributing to otrs_connector
|
14
32
|
|
15
33
|
* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.5.
|
1
|
+
0.5.2
|
data/lib/otrs.rb
CHANGED
@@ -11,8 +11,8 @@ class OTRS
|
|
11
11
|
@@otrs_api_url ||= "https://loalhost/otrs/json.pl"
|
12
12
|
# Username / password combo should be an actual OTRS agent defined on the OTRS server
|
13
13
|
# I have not tested this with other forms of OTRS authentication
|
14
|
-
@@otrs_user ||=
|
15
|
-
@@otrs_pass ||=
|
14
|
+
@@otrs_user ||= 'rails'
|
15
|
+
@@otrs_pass ||= 'rails'
|
16
16
|
|
17
17
|
def self.user
|
18
18
|
@@otrs_user
|
data/otrs_connector.gemspec
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: otrs_connector
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.5.
|
4
|
+
version: 0.5.2
|
5
5
|
prerelease:
|
6
6
|
platform: ruby
|
7
7
|
authors:
|
@@ -141,7 +141,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
|
|
141
141
|
version: '0'
|
142
142
|
segments:
|
143
143
|
- 0
|
144
|
-
hash:
|
144
|
+
hash: 434281716631286809
|
145
145
|
required_rubygems_version: !ruby/object:Gem::Requirement
|
146
146
|
none: false
|
147
147
|
requirements:
|