Skip to content

Instantly share code, notes, and snippets.

Cédric Fabianski cfabianski

Block or report user

Report or block cfabianski

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile

Keybase proof

I hereby claim:

  • I am cfabianski on github.
  • I am cfabianski ( on keybase.
  • I have a public key whose fingerprint is C122 67B3 C238 0BAE 75E5 6573 189A 0D6C 64F9 E873

To claim this, I am signing this object:

cfabianski /
Created Dec 7, 2015 — forked from andreyvit/
tmux cheatsheet

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

# remap prefix to Control + a
cfabianski / rerun-bookmarklet.js
Created Nov 10, 2015 — forked from elandesign/rerun-bookmarklet.js
Rerun failed specs from Jenkins output
View rerun-bookmarklet.js
cfabianski / migration_sql.rb
Created Nov 3, 2015 — forked from caius/migration_sql.rb
`bundle exec rake db:migrate > up.sql; migration_sql.rb < up.sql`
View migration_sql.rb
#!/usr/bin/env ruby
inside_migration = false
previous_line = ""
ARGF.each_line do |line|
# Remove ANSI colours to make shit easier to reason with
line.gsub!(/\e\[(\d+)(;\d+)*m/, "")
if line =~ /Migrating to/

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

  • Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

  • Use production SSL certificates locally. This is annoying

View gist:9887162

Keybase proof

I hereby claim:

  • I am cfabianski on github.
  • I am cfabianski ( on keybase.
  • I have a public key whose fingerprint is 3355 CC25 E6C6 C89B 8404 A9BB BDE4 D563 82D2 7C8E

To claim this, I am signing this object:

View export_pt_label
#!/usr/bin/env ruby
gem 'activesupport'
gem 'pivotal-tracker'
require 'active_support/core_ext/string'
require 'pivotal_tracker'
You can’t perform that action at this time.