GochoMugo

The [debug][debug] module for Node.js is one of the most useful utilities when it comes to high-level debugging. The only problem with using it, would that the module eventually becomes a hard dependency in your project. Your project will NOT run if the package is not installed despite the fact that it is only needed in development mode.

One way to work around this to have a dummy function used in place of the real debug function, when users are in production mode.

var debug = process.env.DEBUG ? require("debug")("MyProject:Server") : function() {};

This way, the module is only loaded when the DEBUG environment variable is set. Therefore, the package can be added as a devDependency to the project's package.json rather than as a dependency.

GochoMugo

Ajv issue - IPv4 address satisfies 'hostname' format (github.com/ajv-validator/ajv/issues/832)

$ npm install
$ node index.js

GochoMugo

Bug report at jdalrymple/gitbeaker#832.

To reproduce the bug:

$ npm install

$ export GITLAB_TOKEN=xxx
$ export GITLAB_PROJECT_ID=xxx

GochoMugo

/*
* This piece of code uses jQuery
*
* I'm also using Showdown to convert my markdown to html. 
* You can get a copy from 
* http://softwaremaniacs.org/playground/showdown-highlight/showdown.js
*
* I'm also using Prism.js from http://prismjs.com/
* to syntax-highlight my code.
*

GochoMugo

Keybase proof

I hereby claim:

• I am GochoMugo on github.
• I am mugo (https://keybase.io/mugo) on keybase.
• I have a public key whose fingerprint is C11B 1DE3 B886 975F 3E1D 5524 7B6A 01CB 57AA 39E4

To claim this, I am signing this object:

GochoMugo

$ msu install-many mods.txt       # assuming the file 'mods.txt' list some modules
$ msu upgrade                     # this upgrades 'msu' to latest release
$ msu nuke                        # this removes msu from this machine

GochoMugo

Once you have created a remindme.cfg with the contents as shown in the file, place it in ~/.mackup.

Now, trigger a backup:

$ mackup backup

GochoMugo

XDK Installation on Debian Wheezy (64-bit)

After installing the XDK, you may realize that it will NOT start. This is due to libc issues with the Node-webkit version installed along with the XDK. To solve this issue, we need to install a compatible version (easy way) or build the lastest node-webkit on our machine.

I only know of the easy way :-). So here it is.

Easy Way

1. Install the XDK, if you have NOT. Take note of where it is installed. Most probably it will be:

GochoMugo

import smtplib, os
from email import Encoders
from email.Utils import COMMASPACE, formatdate
from email.MIMEText import MIMEText
from email.MIMEBase import MIMEBase
from email.MIMEMultipart import MIMEMultipart
import argparse
import sys 

#INFO

GochoMugo

Compiling v8 and Hello, World Example on Mac OSX Mavericks (10.9.4)

by Keith Rosenberg (netpoetica)

Note: do this in some sort of project/ directory that makes sense. depot_tools are going to need to be in your path, so you may want to install them somewhere you are comfortable with.

1) Get the v8 source

git clone https://github.com/v8/v8.git

2) Install depot tools