Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

  • Cannot push ruby gem

    Support ruby
    2
    0 Votes
    2 Posts
    3 Views
    atrippA
    Hello; I'm not all that familiar with Ruby Gems, but I'll try to help. At first, I think the problem is that you're using host instead of source. gem push <gem file> --source http://<redacted>/rubygems/RubyGem Hope that does the trick :) FYI; we recently updated our RubyGems Documentation to help others get setup.
  • Cannot push ruby gem

    Support ruby proget feeds
    3
    0 Votes
    3 Posts
    21 Views
    ?
    Upgrading to v5 seems to have fixed this
  • Cannot get RubyGems connector to work

    Support ruby proget
    3
    0 Votes
    3 Posts
    26 Views
    ?
    Confirmed that was the issue, thanks Tod.
  • Anonymous access to ruby gem feed

    Support proget ruby
    2
    0 Votes
    2 Posts
    15 Views
    ?
    This should work as you describe if you grant the user "Anonymous" the "View and Download Packages" task for the gems feed.
  • SQL error on Gem push/upload to endpoint

    Support linux ruby proget
    2
    0 Votes
    2 Posts
    10 Views
    ?
    Hi Ken, Thanks for contacting us. We are aware of this issue and have traced it to be a bug in a database script, that only affects Linux. The good news is we already have issued a fix for the problem (https://inedo.myjetbrains.com/youtrack/issue/PG-1101), it just needs to be reviewed and tested.
  • Ruby feed is not working

    Support feeds proget ruby
    2
    0 Votes
    2 Posts
    16 Views
    ?
    The url is wrong, and we will update this in the next maintence release
  • Ruby Gems

    Support ruby proget
    2
    0 Votes
    2 Posts
    7 Views
    ?
    Most definitely :) We don't have a target date just yet, but it's on our ProGet Roadmap. I'll add a +1 to the feature. Thanks.
  • Is Ruby Gem support on the horizon?

    Support proget ruby
    2
    0 Votes
    2 Posts
    10 Views
    ?
    Most definitely; it's a must-have as we transition from a "private NuGet server" to a "private repository manager". I suppose we should explicitly list it under "New repository formats". I'll add a +1 to our (internal) tracker!
  • Rubygems feeds

    Support feeds ruby proget
    2
    0 Votes
    2 Posts
    9 Views
    ?
    It's not possible to add a new feed type via the SDK, but it's for sure on our roadmap.
  • Downloading packages from LDAP-Authticated feeds in Ruby

    Support ruby proget
    3
    0 Votes
    3 Posts
    13 Views
    ?
    Answering my own question using this solution. Hope anyone else who has to do this with Ruby will find this helpful: require 'rubygems' require 'httpclient' #latest, with rubyntlm also installed http_client = HTTPClient.new http_client.set_auth(nil, '<domain>\<username>', '<password>') local_file = File.new("C:\\temp\\<package>.<version>.nupkg", "wb") local_file.write( http_client.get_content("https://<server>/nuget/<feed>/package/<package>/<version>") ) -/- flagellum
  • BuildMaster deployments vs. Rails Migration

    Support ruby buildmaster
    2
    0 Votes
    2 Posts
    9 Views
    ?
    First and foremost, it's not a "competing" process, but more of a complimentary one. That is, BuildMaster can be used to automate a RoR deployment via the RAKE action. If you're using db:migrate, this is handled via the RAKE action in the exact same manner. If you'd like to try more advanced database development (as RoR's database support does not use features such as triggers or foreign key constraints), then BuildMaster's change script feature is available for you to try. The primary benefits to doing this are the added dimensions/concepts of applications, releases, builds, promotions, etc. - instead of just files and (possibly) changesets. For small, part-time hobby projects, these benefits are akin to the benefits added by source control and/or issue tracking - just about beneficial enough to use, but not enough to pay for (thus why we have the free edition.)