LM lucasmodrich

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example

Securing you Linux Computer (Raspberry Pi)

This was inspired by the concise works of jeff's Skinner Box

Primary Article to begin with:

HowTo: Set-Up the Raspberry Pi as a Headless Device

Lets make sure that we have all the sheilds up!

Protect your Network

The MIT License (MIT)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

Fonte: http://brandon.invergo.net/news/2012-05-26-using-gnu-stow-to-manage-your-dotfiles.html?round=two

I accidentally stumbled upon something yesterday that I felt like sharing, which fell squarely into the "why the hell didn't I know about this before?" category. In this post, I'll describe how to manage the various configuration files in your GNU/Linux home directory (aka "dotfiles" like .bashrc) using GNU Stow.

The difficulty is that it would be helpful to manage one's configuration files with a version control system like Git, Mercurial or Bazaar, but many/most dotfiles reside at the top-level of your home directory, where it wouldn't be a good idea to initialize a VCS repository. Over time I've come across various programs which aim to manage this for you by keeping all the files in a subdirectory and then installing or linking them into their appropriate places. None of those programs ever really appealed to me. They would require a ton of dependencies (like Ruby and a ton of libraries for it) or t

Converting a Word Document to Markdown in Two Moves

The Problem

A lot of important government documents are created and saved in Microsoft Word (*.docx). But Microsoft Word is a proprietary format, and it's not really useful for presenting documents on the web. So, I wanted to find a way to convert a .docx file into markdown.

The Solution

As it turns out, there are several open-source tools that allow for conversion between file types. Pandoc is one of them, and it's powerful. In fact, pandoc's website says "If you need to convert files from one markup format into another, pandoc is your swiss-army knife." But, although pandoc can convert from markdown into .docx, it doesn't work in the other direction.

	$ErrorActionPreference = "Stop"

	$NewtonsoftJsonPath = Resolve-Path -Path "bin\Newtonsoft.Json.dll"
	$NewtonsoftJsonSchemaPath = Resolve-Path -Path "bin\Newtonsoft.Json.Schema.dll"

	Add-Type -Path $NewtonsoftJsonPath
	Add-Type -Path $NewtonsoftJsonSchemaPath

	$source = @'
	public class Validator

	# one or the other, NOT both

	[url "https://github"]
	insteadOf = git://github

	# or

	[url "[email protected]:"]
	insteadOf = git://github

	-- VARCHAR TO Base64
	IF OBJECT_ID (N'[dbo].[uFnStringToBase64]', N'FN') IS NOT NULL
	DROP FUNCTION uFnStringToBase64;
	GO
	CREATE FUNCTION [dbo].[uFnStringToBase64]
	(
	@InputString VARCHAR(MAX)
	)
	RETURNS VARCHAR(MAX)
	AS

	#!/bin/bash
	# Build a commit frequency list.

	ROW_LIMIT=20

	git log --name-status $* \| \
	grep -E '^[A-Z]\s+' \| \
	cut -c3-500 \| \
	sort \| \
	uniq -c \| \

	# Generate PDFs from the Markdown source files
	#
	# In order to use this makefile, you need some tools:
	# - GNU make
	# - Pandoc
	# - LuaLaTeX
	# - DejaVu Sans fonts

	# Directory containing source (Markdown) files
	source := src