You have a git commit in your history that is causing a bug but you do not know which commit it is.
Here's how to use git bisect to find the commit that causes the bug.
# in the git root, start the git bisect
git bisect start
# mark current commit as bad
git bisect bad
| # Generates necessary certificates to ~/.docker | |
| # | |
| # Usage: | |
| # bundle install | |
| # ruby certgen.rb <domain> | |
| require 'certificate_authority' | |
| require 'fileutils' | |
| if ARGV.empty? |
Yet another framework syndrome
| Name | Date | URL | Stars |
|---|---|---|---|
| Jake | April 2010 | https://github.com/mde/jake | 1000 |
| Brunch | January 2011 | http://brunch.io/ | 3882 |
| #!/bin/bash | |
| # | |
| # This file is managed by Chef, using the <%= node.name %> cookbook. | |
| # Editing this file by hand is highly discouraged! | |
| # | |
| # Copyright (c) 2014 Jean Mertz <[email protected]> | |
| # | |
| # Permission is hereby granted, free of charge, to any person obtaining a copy | |
| # of this software and associated documentation files (the "Software"), to deal |
| d3.select("#save").on("click", function(){ | |
| var html = d3.select("svg") | |
| .attr("version", 1.1) | |
| .attr("xmlns", "http://www.w3.org/2000/svg") | |
| .node().parentNode.innerHTML; | |
| //console.log(html); | |
| var imgsrc = 'data:image/svg+xml;base64,'+ btoa(html); | |
| var img = '<img src="'+imgsrc+'">'; | |
| d3.select("#svgdataurl").html(img); |
| // Start `node d3-server.js` | |
| // Then visit http://localhost:1337/ | |
| // | |
| var d3 = require('d3'), | |
| http = require('http') | |
| http.createServer(function (req, res) { | |
| // Chrome automatically sends a requests for favicons | |
| // Looks like https://code.google.com/p/chromium/issues/detail?id=39402 isn't | |
| // fixed or this is a regression. |
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
