A list of the most common functionalities in Jekyll (Liquid). You can use Jekyll with GitHub Pages, just make sure you are using the proper version.
Running a local server for testing purposes:
A list of the most common functionalities in Jekyll (Liquid). You can use Jekyll with GitHub Pages, just make sure you are using the proper version.
Running a local server for testing purposes:
| # Goal: put a non-Rails-aware Ruby library using normal `require`s in | |
| # lib/sim. Have it transparently reloaded between requests like Rails app | |
| # code is. | |
| # | |
| # The code here goes inside of your configure block in | |
| # config/environments/development.rb. There are two parts, commented inline. | |
| # Reload code whenever the simulator changes. | |
| config.watchable_dirs["lib/sim"] = [:rb] | |
| config.watchable_files << "lib/sim.rb" |
| Ruby 2.1.0 in Production: known bugs and patches | |
| Last week, we upgraded the github.com rails app to ruby 2.1.0 in production. | |
| While testing the new build for rollout, we ran into a number of bugs. Most of | |
| these have been fixed on trunk already, but I've documented them below to help | |
| anyone else who might be testing ruby 2.1 in production. | |
| @naruse I think we should backport these patches to the ruby_2_1 branch and | |
| release 2.1.1 sooner rather than later, as some of the bugs are quite critical. | |
| I'm happy to offer any assistance I can to expedite this process. |
THIS GIST WAS MOVED TO TERMSTANDARD/COLORS REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
| module Reportable | |
| extend ActiveSupport::Concern | |
| module ClassMethods | |
| # Chain on a scope and specify the fields to extract. | |
| # Example: | |
| # User.enabled.report %{ | |
| # :email_opt_in, | |
| # 'created_at as sign_up_date' | |
| # } |
Time: 25-30 minutes.
Goal: Better back, front, and overhead squats. Very basic gymnastic conditioning.
"Limber 11" ([video][limber-11])
| run "sed --in-place '/turbolinks/d' Gemfile" | |
| run "sed --in-place '/turbolinks/d' app/assets/javascripts/application.js" | |
| run "sed --in-place '/coffee/d' Gemfile" | |
| run "sed --in-place '/jbuilder/d' Gemfile" | |
| run "sed --in-place 's/, \"data-turbolinks-track\" => true//' app/views/layouts/application.html.erb" | |
| gem 'active_model_serializers' |
I'm writing in response to events that have recently come to light involving a sexual assault at a tech conference. Background information can be found [here][1], [here][2], and [here][3] as well as on twitter and google.
I've been watching this from the sidelines, and I've been wrestling with several questions that I can't seem to shake and that I really don't have answers to.
I wear many hats, both in the tech community and others. I'm a coder, a speaker, a user group organizer, a conference organizer, and even a boss. Each of those roles colors how I see this, but there's one role that is overpowering in my reaction.
See, I'm a Dad. A dad of two beautiful and innocent girls who are 3 and 2. They have their whole lives in front of them and so the questions I'm struggling with are:
@holman got a request about our deployment system, heaven
I know it's not a high priority, but has there been any activity on open-sourcing the core Heaven gem?
There is. I've been working on extracting the non-GitHub specific parts into two gems. This first is a CLI portion called hades. The second is an HTTP API portion called heaven.
When you open source something previously used as in internal tool like Heaven, Hubot, Boxen, etc., how do you manage and hook in the parts that need to stay internal?
Normally I focus around four questions:
| " Search Dash for word under cursor | |
| function! SearchDash() | |
| let s:browser = "/usr/bin/open" | |
| let s:wordUnderCursor = expand("<cword>") | |
| let s:url = "dash://".s:wordUnderCursor | |
| let s:cmd ="silent ! " . s:browser . " " . s:url | |
| execute s:cmd | |
| redraw! | |
| endfunction | |
| map <leader>d :call SearchDash()<CR> |