gemstash | A RubyGems.org cache and private gem server | Continous Integration library

by rubygems Ruby Version: v2.2.2 License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | gemstash Summary

gemstash is a Ruby library typically used in Devops, Continous Integration, Ruby On Rails applications. gemstash has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Gemstash is both a cache for remote servers such as and a private gem source. If you are using bundler across many machines that have access to a server within your control, you might want to use Gemstash. If you produce gems that you don’t want everyone in the world to have access to, you might want to use Gemstash. If you frequently bundle the same set of gems across multiple projects, you might want to use Gemstash. Are you only using gems from and don’t bundle the same gems frequently? Well, maybe you don’t need Gemstash… yet. Gemstash is maintained by Ruby Together, a grassroots initiative committed to supporting the critical Ruby infrastructure you rely on. Contribute today as an individual or even better, as a company, and ensure that Bundler, RubyGems, Gemstash, and other shared tooling is around for years to come.

Support

Quality

Security

License

Reuse

Support

gemstash has a low active ecosystem.

It has 703 star(s) with 125 fork(s). There are 19 watchers for this library.

It had no major release in the last 6 months.

There are 33 open issues and 81 have been closed. On average issues are closed in 377 days. There are 6 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of gemstash is v2.2.2

Quality

gemstash has 0 bugs and 0 code smells.

Security

gemstash has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

gemstash code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

gemstash is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

gemstash releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed gemstash and discovered the below as its top functions. This is intended to give you an instant insight into gemstash implemented functionality, and help decide if they suit your requirements.

Deletes the content from the cache
Make a HTTP request
Update properties of the resource
Get Redis cache
Create a new zip object .
Determines the path to the Gemfile .
Displays display commands .
Check if the expected output matches the expected output
Clears the Gemfile for the Gemfile
Executes the command in the binary instance .

Get all kandi verified functions for this library.

gemstash Key Features

No Key Features are available at this moment for gemstash.

gemstash Examples and Code Snippets

No Code Snippets are available at this moment for gemstash.

Community Discussions

Trending Discussions on gemstash

JRuby, gemstash and sqlite3

Use private GemStash repository to install LogStash plugins

Resetting gemstash to original state

QUESTION

JRuby, gemstash and sqlite3

Asked 2018-Jan-28 at 10:35

I'm trying to run gemstash with JRuby, but it seems to have a dependency with sqlite3-1.3.13 which of course fails because it requires a C native extension. I've skimmed the projects issues in github and found nothing about it not beeing compatible with JRuby 9.1.14.0. Is there a workaround to the "sqlite3 won't install in JRuby" thing?

...

ANSWER

Answered 2018-Jan-28 at 10:35

seems that (at least on master), the sqlite3 gem should only load under C-Ruby, while under JRuby jdbc-sqlite3 is expected to be loaded/used.

https://github.com/bundler/gemstash/blob/master/gemstash.gemspec#L48

Source https://stackoverflow.com/questions/48406972

QUESTION

Use private GemStash repository to install LogStash plugins

Asked 2018-Jan-15 at 15:55

I'm currently trying to install private LogStash plugins hosted on a private GemStash registry.

In our architecture, the GemStash registry is a mirror of RubyGems as well as a private Gem hosting server which works well if I directly use the gem or bundler binary in Ruby projects.

The GemStash mirror is available at http://my-domain and the private registry is available at http://my-domain/private.

For installing a private LogStash plugins, we need to reconfigure the LogStash Gemfile according to https://www.elastic.co/guide/en/logstash/current/private-rubygem.html

When configuring LogStash only with my private registry or only with my public registry or even with both sources, LogStash is not able to resolve my plugins.

Basically, to make it working I should be able to generate the following Gemfile with the logstash-plugin install/update command:

...

ANSWER

Answered 2018-Jan-15 at 15:55

Nevermind, replacing the Gemfile source with my two custom domains works well.

The issue was GemStash was load balanced in the AWS cloud and the private directory used to store the private Gems was not shared between the GemStash instances...

Source https://stackoverflow.com/questions/48227936

QUESTION

Resetting gemstash to original state

Asked 2017-Jun-13 at 06:54

Looking through the documentation, I have not found anything that resets the entire cache to the original state. I would like to delete all the gems that have been cached in gemstash. I have tried deleting the gem_cache folder in gemstash, but when I rerun bundle install, nothing is populated in the gem_cache folder. I have figured that it will only populate if all the files related to the gem is deleted in .bundle/ folder. Is there an easier way to do this?

Any help would be appreciated Thanks in advance

...

ANSWER

Answered 2017-Jun-13 at 06:54

Deleting the files and folders in gem_cache is sufficient for resetting the cache. To repopulate the cache, make sure the file Gemfile.lock is deleted, to ensure that the dependencies are fetched from the source again. This means that it when fetching the dependencies, it would go through the gemstash, and therefore cached.

Source https://stackoverflow.com/questions/44473261

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install gemstash

Gemstash is designed to be quick and painless to get set up. By the end of this Quickstart Guide, you will be able to bundle stashed gems from public sources against a Gemstash server running on your machine.

Support

Bug reports and pull requests are welcome on GitHub at https://github.com/rubygems/gemstash. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

Find more information at: