Older Rails versions used to use the Quiet Assets GEM which was then rolled directly into the Rails asset pipeline with

 # config/environments/development.rb config.assets.quiet = true 

This switch works with Webrick and the development.log file, but I usually code with Webrick and byebug for debugging, so I have the console open and am always reading the STDOUT stream. The Asset logging stream is NOT silenced from the STDOUT so my console is still hopelessly cluttered.

Ruby monkey-patching to the rescue:

 if Rails.env.development? && defined?(::WEBrick) # Stop all the /assets/ logs in the webrick stdout module WEBrick...
      

Assuming you are using Ruby Installer to install Ruby on Windows, getting Ruby to make a call to an HTTPS server isn’t straightforward.

 Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Administrator>ruby -v ruby 2.2.4p230 (2015-12-16 revision 53155) [i386-mingw32] C:\Users\Administrator>ruby -ropenssl -e 'puts OpenSSL::X509::DEFAULT_CERT_FILE' C:/Users/Justin/Projects/knap-build/var/knapsack/software/x86-windows/openssl/1.0.1l/ssl/cert.pem C:\Users\Administrator> C:\Users\Administrator>ruby -ropenssl -ve 'puts Gem::VERSION, OpenSSL::OPENSSL_VERSION' ruby 2.2.4p230 (2015-12-16 revision 53155) [i386-mingw32] 2.6.6 OpenSSL 1.0.1l 15 Jan 2015 

If you look at the default SSL cert file, you will notice that it is set to the path by the developer that packaged Ruby Installer.

So if you...