# Windows Pushy Client install

**URL:** <https://discourse.chef.io/t/windows-pushy-client-install/6295>\
**Category:** Chef Infra (archive)\
**Created:** [February 13, 2015, 4:20pm UTC](https://discourse.chef.io/t/windows-pushy-client-install/6295 "2015-02-13T16:20:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Pimentel](https://avatars.discourse-cdn.com/v4/letter/m/9f8e36/32.png) [@Mark\_Pimentel](https://discourse.chef.io/u/Mark_Pimentel)\
**Post date:** [February 13, 2015, 4:20pm UTC](https://discourse.chef.io/t/windows-pushy-client-install/6295/1 "2015-02-13T16:20:06Z")

</div>

I just installed the pushy client on a windows 2008r2 server with chef  
12.0.3 already installed and noticed it completely hijacks chef’s own GEM  
path causing all attempts to load other gems to fail.

------ gem env ------  
RubyGems Environment:

- RUBYGEMS VERSION: 1.8.28
- RUBY VERSION: 1.9.3 (2013-11-22 patchlevel 484) [i386-mingw32]
- INSTALLATION DIRECTORY: C:/opscode/pushy/embedded/lib/ruby/gems/1.9.1
- RUBY EXECUTABLE: C:/opscode/pushy/embedded/bin/ruby.exe
- EXECUTABLE DIRECTORY: C:/opscode/pushy/embedded/bin
- RUBYGEMS PLATFORMS:
  - ruby
  - x86-mingw32

- GEM PATHS:
  - C:/opscode/pushy/embedded/lib/ruby/gems/1.9.1
  - C:/Users/Administrator/.gem/ruby/1.9.1

- GEM CONFIGURATION:
  - :update\_sources =\> true
  - :verbose =\> true
  - :benchmark =\> false
  - :backtrace =\> false
  - :bulk\_threshold =\> 1000

- REMOTE SOURCES:
  - [http://rubygems.org/](http://rubygems.org/)

The install was used via the push-jobs cookbook.

Anyone else notice this?

–  
Thanks,

Mark

---

<div class="post-metadata">

**Author:** ![Morgan\_Blackthorne](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/morgan_blackthorne/32/100_2.png) [@Morgan\_Blackthorne](https://discourse.chef.io/u/Morgan_Blackthorne)\
**Post date:** [February 13, 2015, 4:23pm UTC](https://discourse.chef.io/t/windows-pushy-client-install/6295/2 "2015-02-13T16:23:13Z")

</div>

Last I had checked pushy wasn't available for Windows; nice to see they're  
closing that gap. Maybe x86 and not insisting on runit under Linux will  
come down the pipe as well...  
On Feb 13, 2015 8:20 AM, "Mark Pimentel" [markpimentel22@gmail.com](mailto:markpimentel22@gmail.com) wrote:

> I just installed the pushy client on a windows 2008r2 server with chef  
> 12.0.3 already installed and noticed it completely hijacks chef's own GEM  
> path causing all attempts to load other gems to fail.
> 
> ------ gem env ------  
> RubyGems Environment:
> 
> - RUBYGEMS VERSION: 1.8.28
> - RUBY VERSION: 1.9.3 (2013-11-22 patchlevel 484) [i386-mingw32]
> - INSTALLATION DIRECTORY: C:/opscode/pushy/embedded/lib/ruby/gems/1.9.1
> - RUBY EXECUTABLE: C:/opscode/pushy/embedded/bin/ruby.exe
> - EXECUTABLE DIRECTORY: C:/opscode/pushy/embedded/bin
> - RUBYGEMS PLATFORMS:
> - ruby
> - x86-mingw32
> 
> - GEM PATHS:
> - C:/opscode/pushy/embedded/lib/ruby/gems/1.9.1
> - C:/Users/Administrator/.gem/ruby/1.9.1
> 
> - GEM CONFIGURATION:
> - :update\_sources =\> true
> - :verbose =\> true
> - :benchmark =\> false
> - :backtrace =\> false
> - :bulk\_threshold =\> 1000
> 
> - REMOTE SOURCES:
> - [http://rubygems.org/](http://rubygems.org/)
> 
> The install was used via the push-jobs cookbook.
> 
> Anyone else notice this?
> 
> --  
> Thanks,
> 
> Mark