Instance | Branch |
---|
# /etc/security/limits.conf | |
* soft nofile 999999 | |
* hard nofile 999999 | |
root soft nofile 999999 | |
root hard nofile 999999 | |
=========================================================== | |
# /etc/sysctl.conf | |
# sysctl for maximum tuning |
##How To Reset Your Github Fork
Let’s say I want to contribute to a project on github. The project repository is at wp-cli/wp-cli. First I fork it, and then clone the resulting repository, scribu/wp-cli:
git clone --recursive [email protected]:scribu/wp-cli.git
cd wp-cli
Now, I make some commits to master, push them to my fork and open a pull request. Piece of cake:
git commit -m "awesome new feature"
#!/bin/bash | |
# Downloads and applies a patch from Drupal.org. | |
if [ -z "$1" ] | |
then | |
echo "You need to supply a URL to a patch file." | |
exit | |
fi | |
URL=$1; |
While the following structure is not an absolute requirement or enforced by the tools, it is a recommendation based on what the JavaScript and in particular Node community at large have been following by convention.
Beyond a suggested structure, no tooling recommendations, or sub-module structure is outlined here.
lib/
is intended for code that can run as-issrc/
is intended for code that needs to be manipulated before it can be used
from __future__ import division, print_function | |
import numpy as np | |
from scipy import signal | |
import matplotlib.pyplot as plt | |
def plot_response(fs, w, h, title): | |
plt.figure() | |
plt.plot(0.5*fs*w/np.pi, 20*np.log10(np.abs(h))) |
- Arduino
- The Handy Board
- Handyboard Hacker's Resource Guide
- [The Handy Cricket](http://www.handyboard.com/cricket" ADD_DATE="908235315" LAST_VISIT="935879243" LAST_MODIFIED="908235252)
- Blackfin Handyboard (in Development)
- OOPic: Object-Oriented Programmable Integrated Circuit
- Parallax BASIC Stamp Microcontrollers
- Sumo11 Robot Controller
- IntelliBrain Robot Controller
In this article, I will share some of my experience on installing NVIDIA driver and CUDA on Linux OS. Here I mainly use Ubuntu as example. Comments for CentOS/Fedora are also provided as much as I can.
Host *+* | |
ProxyCommand ssh $(echo %h | sed 's/+[^+]*$//;s/\([^+%%]*\)%%\([^+]*\)$/\2 -l \1/;s/:/ -p /') exec nc -w1 $(echo %h | sed 's/^.*+//;/:/!s/$/ %p/;s/:/ /') |
'use strict'; | |
////////////////////////////////// | |
// How to use? | |
// 1. Create `sequelize-schema-file-generator.js` in your app root | |
// 2. Make sure you've ran the `sequelize init` before (It should create `config`,`seeders`,`migrations` folders). | |
// 3. Update `DATABASE_DSN` below to match your connection string (works with any database adapter that Sequelize supports) | |
// 4. Run it with `node sequelize-schema-file-generator.js` | |
// 5. Review the generated migrations inside of the `migrations` folder. | |
////////////////////////////////// |