Skip to content

Instantly share code, notes, and snippets.

View rogeriopradoj's full-sized avatar
😀

Rogerio Prado de Jesus rogeriopradoj

😀
View GitHub Profile

Deploying Sculpin Sites to GitHub Pages

I wanted to be able to use Sculpin to generate GitHub pages. Here's what I did...

  1. Created a super awesome Sculpin site from the Sculpin Blog Skeleton

  2. Make sure everything is under version control in my master branch (except things that shouldn't be. see the .gitignore)

  3. Updated publish.sh:

#!/bin/bash

# install
update-rc.d btsyncd defaults

# uninstall
/etc/init.d/btsyncd stop
rm -rf /etc/init.d/btsyncd
rm -rf /DataVolume/cache/btsync/

update-rc.d -f btsync remove

Spurred by recent events (https://news.ycombinator.com/item?id=8244700), this is a quick set of jotted-down thoughts about the state of "Semantic" Versioning, and why we should be fighting the good fight against it.

For a long time in the history of software, version numbers indicated the relative progress and change in a given piece of software. A major release (1.x.x) was major, a minor release (x.1.x) was minor, and a patch release was just a small patch. You could evaluate a given piece of software by name + version, and get a feeling for how far away version 2.0.1 was from version 2.8.0.

But Semantic Versioning (henceforth, SemVer), as specified at http://semver.org/, changes this to prioritize a mechanistic understanding of a codebase over a human one. Any "breaking" change to the software must be accompanied with a new major version number. It's alright for robots, but bad for us.

SemVer tries to compress a huge amount of information — the nature of the change, the percentage of users that wil

Index: pt_BR/appendices/comparisons.xml
===================================================================
--- pt_BR/appendices/comparisons.xml (revision 335264)
+++ pt_BR/appendices/comparisons.xml (working copy)
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="utf-8"?>
-<!-- EN-Revision: 311459 Maintainer: fibbarth Status: ready -->
-<!-- CREDITS: narigone -->
+<!-- EN-Revision: 331317 Maintainer: fibbarth Status: ready -->
+<!-- CREDITS: narigone, Nawarian Níckolas -->
Index: appendices/ini.core.xml
===================================================================
--- appendices/ini.core.xml (revision 335516)
+++ appendices/ini.core.xml (working copy)
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="utf-8"?>
-<!-- EN-Revision: 329119 Maintainer: fibbarth Status: ready -->
+<!-- EN-Revision: 329119 Maintainer: fibbarth Status: wip --><!-- CREDITS: fibbarth, henriquemoody -->
<section xml:id="ini.core" xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink">
# Worked under these envelopment
#
# AMI: amzn-ami-pv-2012.09.0.x86_64-ebs (ami-4e6cd34f)
# Zone: ap-northeast-1b
# Type: m1.large
#
# CentOS phpenv (https://github.com/CHH/phpenv) system wide installation script
# Execute as root user.
# Set group to use phpenv:
# Worked under these envelopment
#
# AMI: amzn-ami-pv-2012.09.0.x86_64-ebs (ami-4e6cd34f)
# Zone: ap-northeast-1b
# Type: m1.large
#
# CentOS phpenv (https://github.com/CHH/phpenv) system wide installation script
# Execute as root user.
# Set group to use phpenv:
// iMacro CheatSheet - Command Reference
// http://wiki.imacros.net/Command_Reference
// iMacros supports 3 types of variables:
// * The macro variables !VAR0 thru !VAR9. They can be used with the SET and ADD command inside a macro.
// * Built-in variables. They contain certain values set by iMacros.
// * User-defined variables. They are defined in-macro using the SET command.

Setup modern.ie vagrant boxes

Since modern.ie released vagrant boxes, it' no longer necessary to manually import the ova file to virtualbox, as mentioned here.

However, the guys at modern.ie didn't configured the box to work with WinRM. This how-to addresses that, presenting steps to proper repackage these boxes, adding WinRM support. Additionally configures chocolatey package manager and puppet provisioner.

Pre-requisites

@rogeriopradoj
rogeriopradoj / gist:cf2c8ed9a05449d8513dd6c614f88cd5
Created April 21, 2016 16:09 — forked from NoobsArePeople2/gist:4490307
Configuration for .bash_profile on OSX to get some Posh-Git features.
  1. Open Terminal move to your home folder: cd ~

  2. Enable git colors: git config --global color.ui true

  3. Make a file called ".colors": touch .colors

  4. Open .colors and paste the following: