<commit_before>= gem-manage-sources

gem-manage-sources is a replacement for the 'gem sources' command that allows you to easily use sources that may not always be available.

Imagine you work at a company that hosts its own gem server within the corporate network.  At work you need to install and update gems hosted on the corporate
server, but when you take your laptop home and try to work on some side projects (that don't use the company gems) all your remote gem commands fail.  So, you end up typing 'gem sources -a' and 'gem sources -r' a lot.

gem-manage-sources solves this problem by maintaining two list of gem servers (active and inactive) and checking whether or not gem servers are available.  If a server is unavailable it gets put on the inactive list and removed form your gem sources.  When it becomes availabl again it gets re-added to your list of gem sources.

== Installation

  gem install gem-manage-sources

== Usage

Before you use gem-manage-sources you need to initialize the lists of gem sources using:

  gem manage_sources --init

Now whenever you switch networks or want to check whether some of your sources are available use:

  gem manage_sources --check

gem-manage-sources is effectively a replacement for
  
  gem sources

In order to keep your gem sources in sync you should always use 
  
  gem manage_sources --add
  gem manage_sources --remove

in place of

  gem sources -a
  gem sources -r

I consider monkey-patching all of this functionality into the existing sources command, but that seemed really intrusive, especially before the whole idea has proven out.

== Links

* Bugtracker: http://github.com/britt/gem-manage-sources/issues
* Code Metrics: http://bit.ly/6CJtPx

== TODO

* JRuby (and *Ruby) support
* Find a better name

== Note on Patches/Pull Requests<commit_msg>Updated README to reflect the new approach<commit_after>= gem-check-sources

gem-check-sources keeps your local list of gem sources in sync and removes any gem servers that might be unavailable.

== Why?

Imagine you work at a company that hosts its own gem server within the corporate network.  At work you need to install and update gems hosted on the corporate
server, but when you take your laptop home and try to work on a side project all your remote gem commands fail.  

So, you end up typing 'gem sources -a' and 'gem sources -r' a lot.

gem-check-sources solves this problem by maintaining two list of gem servers (active and inactive).  If a server is unavailable it gets put on the inactive list and removed from your gem sources.  It will get added back when it becomes available again.

== Installation

  gem install gem-manage-sources

== Usage

  gem check_sources

That's it.  If something is inactive and you want to add it back just run the command again.

== Links

* Issue tracking: http://github.com/britt/gem-manage-sources/issues
* Code Metrics: http://bit.ly/6CJtPx

== Note on Patches/Pull Requests
{'fraction_non_alphanumeric': 0.051203797897592405, 'fraction_numerical': 0.0006781959986436081, 'mean_word_length': 3.85996705107084, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7093918', 'n_tokens_mistral': 797, 'n_tokens_neox': 750, 'n_words': 442}