Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Fix server path configuration in development

This fixes path problems when setting up a local
development environment. In dev, Fog uses the 
local storage provider and Indexer assumes all
operations will result in files being written 
to `Pusher.server_path + "/gems"`. With Fog in the
mix, this actually becomes `Pusher.server_path +
s3_bucket + "/gems"`. (`Pusher.server_path` 
defaults to the `server` directory.)

Removing the s3_bucket name from `rubygems.yml`
and the `'gems'` from `Indexer#fog` means that 
gems and index updates are served out of the
`Pusher.server_path` as expected.

No tests for this as the behavior only occurs in
the development environment.
  • Loading branch information...
commit fe362b416bb352eb3bb3de2681c01cb9942905bf 1 parent df2d3b4
@elskwid elskwid authored
Showing with 2 additions and 2 deletions.
  1. +1 −1  app/jobs/indexer.rb
  2. +1 −1  config/rubygems.yml
View
2  app/jobs/indexer.rb
@@ -31,7 +31,7 @@ def directory
def fog
$fog || Fog::Storage.new(
:provider => 'Local',
- :local_root => Pusher.server_path('gems')
+ :local_root => Pusher.server_path
)
end
View
2  config/rubygems.yml
@@ -3,7 +3,7 @@ development:
local_storage: true
redirector: false
delivery_method: :sendmail
- s3_bucket: development.s3.rubygems.org
+ s3_bucket: ""
s3_domain: development.s3.rubygems.org
cf_domain: development.cf.rubygems.org
asset_cacher: false
Please sign in to comment.
Something went wrong with that request. Please try again.