Elia's weblog

Custom Colorized Environment String in Rails Console

Ever opened a Rails console and wondered “wait, which environment am I in again?” Yeah, me too. Especially when you’re switching between development, staging, and production faster than you can say <code>User.destroy_all</code>. Here’s a neat trick to add some color to your console prompt so you never have to wonder again. <h2>The Problem</h2> The default Rails console visual feedback stops being useful because staging environments are usually configured as “production” on Heroku and most deployment platforms. So <code>Rails.env.production?</code> returns true for both staging and production. Fun times! <h2>The Solution</h2> Drop this into <code>config/initializers/console.rb</code>: <div class="highlight"><pre class="highlight ruby"><code># frozen_string_literal: true require "rails/commands/console/irb_console" module IRBConsoleWithDeployEnv def initialize(app, env) super(app) @deploy_env = env end def colorized_env IRB::Color.const_set(:DIM, 2) unless defined?(IRB::Color::DIM) return super unless @deploy_env IRB::Color.colorize("live:", [:DIM]) + case @deploy_env when "staging" IRB::Color.colorize("stag", [:YELLOW]) when "production" IRB::Color.colorize("prod", [:RED]) else IRB::Color.colorize(@deploy_env, [:BLUE]) end end Rails::Console::IRBConsole.prepend self end </code></pre></div> And this into <code>config/application.rb</code>: <div class="highlight"><pre class="highlight ruby"><code>module MyApp class Application < Rails::Application # Other configurations... console do |app| config.console = Rails::Console::IRBConsole.new(app, ENV["DEPLOY_ENV"]) end end end </code></pre></div> Now your console prompt will show a nice colorized environment string prefixed by your app name. No more “oops, wrong environment” moments.

Feb 16, 2022 git · development · pairing

Add Co-Authored-By to all commits after pairing

<h3>TL;DR</h3> Here’s the full solution: <div class="highlight"><pre class="highlight shell"><code>git filter-branch --msg-filter "ruby -e'puts [$stdin.read,nil,*ARGV].join(%{\\n})' -- 'Co-Authored-By: John Doe <[email protected]>'" origin/master..HEAD </code></pre></div> Now let’s break it down, piece by piece. <h2>The commits</h2> This will list all commits that are in your branch but not on <code>origin/master</code> <div class="highlight"><pre class="highlight shell"><code>origin/master..HEAD </code></pre></div> <h2>The filter</h2> The simplest ruby script that will: <ol> <li>read the original commit message from <code>$stdin</code></li> <li>append any provided argument with a new line</li> </ol> <div class="highlight"><pre class="highlight ruby"><code>puts [ $stdin.read, nil, # extra empty line, for good measure *ARGV ].join(%{\n}) </code></pre></div> And we use <code>--</code> to separate file names to execute from CLI arguments: <div class="highlight"><pre class="highlight shell"><code>$ ruby -e 'p ARGV' -- "anything after '--'" "ends up in ARGV" ["anything after '--'", "ends up in ARGV"] </code></pre></div> <h2>Putting it all together</h2> We’re lucky <code>git filter-branch</code> has an option for changing commit messages, we’ll use that to append <code>Co-Authored-By: …</code> information to every commit in the current branch. The <code>--msg-filter</code> option will execute a script that will take the old message as its standard input and use the standard output as the new message. <div class="highlight"><pre class="highlight shell"><code>git filter-branch --msg-filter "ruby -e'puts [$stdin.read,nil,*ARGV].join(%{\\n})' -- 'Co-Authored-By: John Doe <[email protected]>'" origin/master..HEAD </code></pre></div>

Sep 1, 2020 git · development · continuos-integration

The git-rebase option no-one knows that will shock your coworkers!

A few weeks ago, a moment before pushing upstream a glorious bug-fix, I ran the test suite locally, just to discover that I broke it! Having lost all confidence in the commit history, I was out for blood, looking for the piece of code that ruined the whole PR! <div class="tenor-gif-embed" data-postid="14001328" data-share-method="host" data-width="100%" data-aspect-ratio="1.5323076923076924"><a href="https://tenor.com/view/survivor-38-survivor38-lauren-oconnell-out-for-blood-gif-14001328">Survivor 38 GIF</a> from <a href="https://tenor.com/search/survivor-gifs">Survivor GIFs</a></div><script type="text/javascript" async src="https://tenor.com/embed.js"></script> With more than a hundred git aliases I consider myself quite a git nerd, so I reached out for a tool I knew: <code>git rebase</code>. My plan was: <ol> <li>mark each commit with <code>edit</code></li> <li>run the test suite with <code>bin/rake</code> at each stop</li> <li>identify the offending commit and fix whatever bugs I encountered</li> <li>amend the commit and call it a day</li> </ol> That didn’t feel right tho, it was too clunky, I had a hunch that I could have done better than this! So, after reading once again the <code>git rebase</code> documentation, this little option popped out: <code>git rebase --exec</code>! <h2>What <code>--exec</code> does to <code>git rebase</code></h2> The magic of <code>--exec</code> is that it will execute a command after each commit in your interactive rebase. If the command fails, it will stop the rebase, allow you to fix whatever needs to be fixed, and move along with <code>git rebase --continue</code>. This means that I was able to swiftly run this command after each commit and ensure that I had a green suite at every step of the PR. <div class="highlight"><pre class="highlight shell"><code>git rebase --interactive --exec "bin/rake" origin/master </code></pre></div> Don’t forget that this neat trick can be used for all kinds of problems, like, for example, running a linter for every commit of a PR.

Nov 4, 2013 opal · ruby · euruko · lightning · talk · 2013

Euruko 2013 Opal lightining talk

For those who missed it here's the lightning talk I gave in Athens at <a href="http://euruko2013.org">Euruko 2013</a> <del>(at minute 17:00)</del>: <a href="http://cl.ly/0F203A093L2b" target="_blank"> <figure> <img src="/assets/euruko-talk-poster.jpg" alt="euruko-talk-poster"/> <figcaption>Downlaod it here</figcaption> </figure> </a>  <ul> <li><del><a href="http://www.ustream.tv/recorded/35065939/highlight/376933">Watch on Ustream</a></del></li> <li><a href="http://cl.ly/3w301C0F1535">The slides (html with embedded video, ~14MB)</a></li> </ul> (beware: the slides in the video have the wrong aspect raito)

Oct 10, 2013 opal · ruby · browser · meh · tabs · spaces

Reading meh's code

<img src="/assets/jonathan-goldsmith-eyes.jpg" alt="jonathan-goldsmith-eyes"/> <blockquote> I don't always read <a href="https://github.com/meh">meh's code</a>… but when I do it, I convert tabs to spaces. </blockquote> The bookmarklet: <kbd> <a style="color:inherit;" href="javascript:e=document.querySelector('div.highlight%3Epre');e.innerHTML=e.innerHTML.replace(/( )+/g,function(s)%7Breturn%20new%20Array((s.length/6/4)+1).join(' ')%7D).replace(/%09/g,'  ')"> ↦ meh` </a> </kbd> (drag it to your bookmark bar) UPDATE: Now works with GitHub expanding tabs to non-breaking-spaces (<a href="https://gist.github.com/elia/7097560">history here</a>)

Aug 21, 2013 opal · ruby · browser · talk · slides · video · rails · javascript · italian

Opal Talk at RubyDay 2013 video availble!

Hey, the talk I gave at this year's (2013) RubyDay is now on youtube! I'll update the post with the slides soon :) (LANGUAGE: Italian). <iframe width="420" height="315" src="//www.youtube.com/embed/O_H9E3VpSOc?rel=0" frameborder="0" allowfullscreen></iframe>

Jul 3, 2013 ruby · rails · rails3 · railsapi · sdoc · documentation · docs · ruby2 · github · api

Past and Future of Ruby and Rails

As a sad orphan of railsapi.com I’m proud to present you valuable links to ruby and rails documentation in SDoc format: Searchable Ruby 2.0 API documentation <a href="http://elia.github.io/railsapi.com/public/doc/ruby-v2.0/" target="_blank">http://elia.github.io/railsapi.com/public/doc/ruby-v2.0/</a> Searchable Rails 3.2 API documentation <a href="http://elia.github.io/railsapi.com/public/doc/rails-v3.2/" target="_blank">http://elia.github.io/railsapi.com/public/doc/rails-v3.2/</a>

Mar 4, 2013 git · autocomplete · shorthand · shortcuts · bash

Autocomplete "git" as "g"

For all you lazy Git bums, here’s how you can type “g” got “git” and still have autocompletion (paste into your ~/.bash_profile or .dotfiles system): <code></code> <pre> alias g='git' complete -o bashdefault -o default -o nospace -F _git g 2>/dev/null \ || complete -o default -o nospace -F _git g </pre>

Feb 12, 2013 pow · jruby · hack · sockets · support

Let jRuby and Pow!™ be happy together

Turns out that <a href="http://pow.cx" target="_blank">Pow!</a> <a href="https://github.com/josh/nack/pull/32#issuecomment-8476565" target="_blank">won’t support jRuby anytime soon</a> but the trick described in <a href="https://github.com/josh/nack/pull/32#issuecomment-8476565" target="_blank">josh/nack#32</a> actually works, so rollup your shirt’s sleeves! Go open <code>node_modules/nack/lib/nack/server.rb</code> inside <code>~/Library/Application Support/Pow/Current</code> and replace <code>sock.close_read</code> on line 132 with: <pre class="ruby"> # WAS: sock.close_read begin sock.close_read rescue IOError raise unless RUBY_ENGINE == 'jruby' end</pre> Happy hacking!

Nov 29, 2012

rvm install opal