Rick Cogley RickCogley

Methods of Signing with GPG

There are now two ways to approach this:

Using gpg and generating keys
Using Kryptonite by krypt.co

This Gist explains how to do this using gpg in a step-by-step fashion. Kryptonite is actually wickedly easy to use-but you will still need to follow the instructions

For using a GUI-based GIT tool such as Tower or Github Desktop, follow the steps here for signing with either GPG or Krypt.co.

Copied from http://code.lancepollard.com/complete-list-of-html-meta-tags/

Basic HTML Meta Tags

<meta charset='UTF-8'>
<meta name='keywords' content='your, tags'>
<meta name='description' content='150 words'>
<meta name='subject' content='your website's subject'>
<meta name='copyright' content='company name'>

Copied from http://code.lancepollard.com/complete-list-of-html-meta-tags/

Basic HTML Meta Tags

<meta charset='UTF-8'>
<meta name='keywords' content='your, tags'>
<meta name='description' content='150 words'>
<meta name='subject' content='your website's subject'>
<meta name='copyright' content='company name'>

How-to setup a simple git push deployment

These are my notes basically. At first i created this gist just as a reminder for myself. But feel free to use this for your project as a starting point. If you have questions you can find me on twitter @thomasf https://twitter.com/thomasf This is how i used it on a Debian Wheezy testing (https://www.debian.org/releases/testing/)

Discuss, ask questions, etc. here https://news.ycombinator.com/item?id=7445545

On the server (example.com)

5 entertaining things you can find with the GitHub Search API

Let's have some command-line fun with curl, [jq][1], and the [new GitHub Search API][2].

Today we're looking for:

The hottest repositories created in the last week.
The oldest user accounts with zero followers. (So sad.)
Issue trends by language.
Clojure projects defying convention.

Markdown and reStructuredText

GitHub supports several lightweight markup languages for documentation; the most popular ones (generally, not just at GitHub) are Markdown and reStructuredText. Markdown is sometimes considered easier to use, and is often preferred when the purpose is simply to generate HTML. On the other hand, reStructuredText is more extensible and powerful, with native support (not just embedded HTML) for tables, as well as things like automatic generation of tables of contents.

	#!/usr/bin/env bash

	# To fix the " gpg: WARNING: unsafe permissions on homedir '/home/path/to/user/.gnupg' " error
	# Make sure that the .gnupg directory and its contents is accessibile by your user.
	chown -R $(whoami) ~/.gnupg/

	# Also correct the permissions and access rights on the directory
	chmod 600 ~/.gnupg/*
	chmod 700 ~/.gnupg

	# FORGE CONFIG (DOT NOT REMOVE!)
	include forge-conf/mydomain.com/before/*;

	server {
	listen 443 ssl;
	listen [::]:443 ssl;
	server_name mydomain.com;
	root /home/forge/mydomain.com/;

	# FORGE SSL (DO NOT REMOVE!)

	#!/usr/bin/env bash

	# Colours picked from https://robinpowered.com/blog/best-practice-system-for-organizing-and-tagging-github-issues/

	###
	# Label definitions
	###
	declare -A LABELS

	# Platform

	" Keeping your lovely 'vimrc' INSIDE of your 'vim' directory is a good idea,
	" if only because it makes it easier to move your config around.

	" If you are using 7.4 exclusively, the following will be enough:
	"
	" on Unix-like systems ~/.vim/vimrc
	" on Windows %userprofile%\vimfiles\vimrc

	" If you use both 7.4 and an older version, or only an older version,
	" the simplest, future-proof, solution is to put this line and only