| Dir.chdir('/Users/akshay/Music') | |
| dupFiles = File.join('**', '* 2.mp3') | |
| Dir.glob(dupFiles).each do |dup| | |
| puts "duplicate file: #{dup}" | |
| if File.exists?(dup) | |
| orig = dup[0..-2] | |
| puts "original file: #{orig}" | |
| if File.exists?(orig) | |
| if File.size(dup) == File.size(orig) | |
| puts "deleting #{dup}" |
When, in special circumstances, we want to prevent a function from being called too often:
Throttling - additional calls to the function are ignored for next n ms.
Debouncing - any call to the function is delayed till n ms have passed since the last call.
Both of these are easy to implement by creating meta-functions that return a wrapped version of original function:
function throttle(func, delay) {
var lastHitDate = 0;
return function() {
openssl req -new -newkey rsa:2048 -nodes -keyout server-cert.key -out server-cert-sign-req.csr
# Country Name (2 letter code) [AU]:US
# State or Province Name (full name) [Some-State]:California
# Locality Name (eg, city) []:
# Organization Name (eg, company) [Internet Widgits Pty Ltd]:Flutterby Labs, Inc.
# Organizational Unit Name (eg, section) []:
# Common Name (eg, YOUR name) []:www.dogo.co
There are two JSON API styles:
The ID style is the easiest to get started with, but requires that your clients be able to guess the URLs for related documents. It also locks your API into a particular URL structure, which may become a problem as your API grows.
The URL style requires less guessing on the client side, and makes clients more resilient to API changes, but is trickier to use with relationships and compound documents.
| ********************************************************** | |
| * Displays a time-height diagram for stations | |
| * Author: John Hinsberger | |
| ********************************************************* | |
| *Bald Mountain* | |
| 'open d01_template.ctl' | |
| 'set background 5' | |
| 'clear' |
| server { | |
| listen 80; | |
| listen [::]:80; | |
| server_name domain.com; | |
| autoindex off; | |
| index index.php index.html; | |
| root /srv/www/domain.com/public; |
| function init() { | |
| var HomePage = React.createClass({ | |
| render: function() { | |
| return <div>Home</div>; | |
| } | |
| }); | |
| var NotFoundPage = React.createClass({ | |
| render: function() { |
I recently ran into a problem where I had a suite of applications hosted on a set of subdomains that all needed to be able to share a single cookie. Any cookies other than the shared cookie needed to stay specific to their subdomain, but this one shared cookie needed to be accessible to any of them. I also wanted to accomplish this using Laravel's Cookie facade.
To accomplish this, there were two issues to solve.
In Laravel 5.1, a feature was added which allows you to add a list of cookie names that should not be encrypted to the EncryptCookies Middleware under the $except array. Check out [the docs](http://laravel.com/docs/5.1/responses#attaching-cookies
I currently use Python for nearly all of my data science and wrangling work these days but usually find myself switching to R to visualize data using ggplot2. This is due in part to ggplot2's general excellence, but also because I had a lot of trouble learning Python's most popular viz library, matplotlib on my own...its homepage is decent enough...but its variety of plotting APIs (--pylab? OOP? %matplotlib???) has led to widely differing examples and best practices among the many online matplotlib guides (not dissimilar to the general problem of trying to practice either Python 2.x or 3.x).
That changed yesterday when I stumbled across [Nicolas P. Rougier's beautifully designed and com
| #!/bin/bash | |
| USER=${1:-sebble} | |
| STARS=$(curl -sI https://api.github.com/users/$USER/starred?per_page=1|egrep '^Link'|egrep -o 'page=[0-9]+'|tail -1|cut -c6-) | |
| PAGES=$((658/100+1)) | |
| echo You have $STARS starred repositories. | |
| echo |
