Create Key (no passphrase and name mirror the key)
ssh-keygen -t rsa -N "" -f ~/.ssh/mirror
%!TEX TS-program = xelatex | |
\documentclass[12pt]{scrartcl} | |
% The declaration of the document class: | |
% The second line here, i.e. | |
% \documentclass[12pt]{scrartcl} | |
% is a standard LaTeX document class declaration: | |
% we say what kind of document we are making in curly brackets, | |
% and specify any options in square brackets. |
#!/bin/sh | |
# Generate a bibtex file just containing those publications cited in | |
# a given pandoc document. To use | |
# | |
# extract_pandoc_bib.sh myfile.markdown | |
# | |
# this will generate `myfile.bib`. | |
bib="$HOME/.pandoc/default.bib" |
use Dancer; | |
use DBI; | |
use File::Spec; | |
use File::Slurp; | |
use Template; | |
set 'database' => File::Spec->tmpdir() . '/dancr.db'; | |
set 'session' => 'Simple'; | |
set 'template' => 'template_toolkit'; | |
set 'logger' => 'console'; |
directory "tmp" | |
file "tmp/hello.tmp" => "tmp" do | |
sh "echo 'Hello' > 'tmp/hello.tmp'" | |
end | |
task :default => 'morning:turn_off_alarm' | |
namespace :morning do | |
desc "Turn off alarm." |
<!DOCTYPE html> | |
<html> | |
<head> | |
<meta charset="utf-8"> | |
<title>Responsive Design Testing</title> | |
<style type="text/css"> | |
body { background: #eee; font-family: sans-serif; margin: 20px; overflow-x: scroll; } | |
.wrapper { width: 6000px } | |
.frame { float: left } | |
h2 { color: hsl(210,10%,7%); margin: 0 0 5px 0; text-shadow: rgba(255,255,255,.75) 0 1px 0; } |
/** | |
* Using Google Apps Script to enhance my gmail filters. | |
* | |
* I constantly receive email that are important for a short period of time (When I order food online!!!!) but after | |
* the email is no longer relative (When I get my food!) I have no need for this email. Sadly they tend to pile up on me | |
* (I eat a lot). | |
* | |
* Anyways you can add this 8hrDelete.gs file to https://script.google.com and set it up on a "Time Driven" trigger at what | |
* ever time you'll like. I run it at midnight | |
*/ |
Jon Warbrick, July 2014, V3.2 (for Ansible 1.7)
First one found from of
At the top of the file there should be a short introduction and/ or overview that explains what the project is. This description should match descriptions added for package managers (Gemspec, package.json, etc.)
Show what the library does as concisely as possible, developers should be able to figure out how your project solves their problem by looking at the code example. Make sure the API you are showing off is obvious, and that your code is short and concise.