torquebox-backstage 1.0.0.beta2 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. data/Gemfile +1 -1
  2. data/README.md +14 -12
  3. data/TORQUEBOX_VERSION +1 -1
  4. data/VERSION +1 -1
  5. metadata +5 -5
data/Gemfile CHANGED
@@ -5,7 +5,7 @@ gem 'haml', '~>3.0'
5
5
  gem 'sass', '~>3.0'
6
6
  gem "tobias-jmx", '0.8'
7
7
  gem 'json', '1.5.1'
8
- gem 'torquebox', '~> 2.0.0.beta'#'~> 2.x.incremental'
8
+ gem 'torquebox', '~> 2.0.0'
9
9
  gem 'tobias-sinatra-url-for', '0.2.1'
10
10
  gem 'rack-accept', '~>0.4.0'
11
11
 
data/README.md CHANGED
@@ -31,18 +31,20 @@ application source.
31
31
 
32
32
  ### As A Gem ###
33
33
 
34
- There are currently no released BackStage gems for TorqueBox 2.x - you will
35
- have to generate the gem from the source:
36
-
37
- 1. Clone the [git repo](https://github.com/torquebox/backstage)
38
-
39
- 2. Build the gem: `jruby -S gem build torquebox-backstage.gemspec`
40
-
41
- 3. Install the gem: `jruby -S gem install torquebox-backstage-1.0.dev.gem`
42
-
43
- 4. deploy backstage using the `backstage` command. You can deploy with security
44
- disabled: `jruby -S backstage deploy`
45
- Or enable security by providing a username/password pair: `jruby -S backstage deploy --secure=username:password`
34
+ A version of the gem that supports TorqueBox 2.0.0.beta2 is currently
35
+ available as a beta itself. You can install it via:
36
+
37
+ jruby -S gem install torquebox-backstage --pre
38
+
39
+ Deploy backstage using the `backstage` command. You can deploy with security
40
+ disabled: `jruby -S backstage deploy`
41
+ Or enable security by providing a username/password pair: `jruby -S backstage deploy --secure=username:password`
42
+
43
+ If you are deploying to the torquebox-server gem, you'll need to provide the
44
+ `$TORQUEBOX_HOME` environment var. You can obtain that from the `torquebox`
45
+ command and set it like so:
46
+
47
+ TORQUEBOX_HOME=`torquebox env torquebox_home` backstage deploy
46
48
 
47
49
  ### From Source ###
48
50
 
data/TORQUEBOX_VERSION CHANGED
@@ -1 +1 @@
1
- 2.0.0.beta2
1
+ 2.0.0
data/VERSION CHANGED
@@ -1,3 +1,3 @@
1
- 1.0.0.beta2
1
+ 1.0.0
2
2
 
3
3
 
metadata CHANGED
@@ -1,8 +1,8 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: torquebox-backstage
3
3
  version: !ruby/object:Gem::Version
4
- prerelease: 6
5
- version: 1.0.0.beta2
4
+ prerelease:
5
+ version: 1.0.0
6
6
  platform: ruby
7
7
  authors:
8
8
  - Tobias Crawley
@@ -12,7 +12,7 @@ autorequire:
12
12
  bindir: bin
13
13
  cert_chain: []
14
14
 
15
- date: 2012-01-12 00:00:00 Z
15
+ date: 2012-04-02 00:00:00 Z
16
16
  dependencies:
17
17
  - !ruby/object:Gem::Dependency
18
18
  name: sinatra
@@ -77,7 +77,7 @@ dependencies:
77
77
  requirements:
78
78
  - - ~>
79
79
  - !ruby/object:Gem::Version
80
- version: 2.0.0.beta
80
+ version: 2.0.0
81
81
  type: :runtime
82
82
  version_requirements: *id006
83
83
  - !ruby/object:Gem::Dependency
@@ -281,7 +281,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
281
281
  requirements: []
282
282
 
283
283
  rubyforge_project:
284
- rubygems_version: 1.8.9
284
+ rubygems_version: 1.8.15
285
285
  signing_key:
286
286
  specification_version: 3
287
287
  summary: BackStage - Queue/Topic/Job/etc viewer for TorqueBox