andresaquino

#Heading 1 ##Heading 2 ###Heading 3 ####Heading 4 #####Heading 5 ######Heading 6

---

Paragraph

andresaquino

Programming Fonts

Input™

Fonts for code from DJR & Font Bureau

https://input.djr.com/

Sudo

A free font for coders by Jens Kutílek

andresaquino

XQuartz & OS/X

1. Install XQuartz

$> brew install xquartz
Updating Homebrew...
==> Downloading https://github.com/XQuartz/XQuartz/releases/download/XQuartz-2.8.1/XQuartz-2.8.1.dmg
==> Downloading from https://github-releases.githubusercontent.com/201858552/97a77400-a5f0-11eb-90ad-2973b8c2dc53?X-Amz-Algorithm=AWS4-
######################################################################## 100.0%
==> Installing Cask xquartz

andresaquino

Real-time PHP-FPM Status

This gist will explain you how to enable an undocumented feature of PHP-FPM which will give a real-time performance stats.

Everybody knows the famous phpinfo() and the page it generates, right? Then the real-time PHP-FPM status page design is very similar.

Some informations from the top are not displayed to avoid security issues.

Enable PHP-FPM Status

andresaquino

Simple Git Workflow For Continuous Delivery

Workflow guidelines:

• master branch is always production-ready, deployable, 100% green test suite
• New development is done on feature branches, with frequent rebasing onto master
• Clean commit history by preferring to rebase instead of merge (git pull is configured to automatically rebase)

Workflow

andresaquino

for oldname in Comprobantes*.xml; do newname=$(xmllint --format $efile | grep -o 'UUID="[^"]*' | sed -e "s/UUID=.//g"); mv ${oldname} ${newname^^}.xml; done

andresaquino

vimdiff cheat sheet

git mergetool

In the middle file (future merged file), you can navigate between conflicts with ]c and [c.

Choose which version you want to keep with :diffget //2 or :diffget //3 (the //2 and //3 are unique identifiers for the target/master copy and the merge/branch copy file names).

cmd	means

andresaquino

# basic pfctl control
# ==
# Related: http://www.OpenBSD.org
# Last update: Tue Dec 28, 2004
# ==
# Note:
# this document is only provided as a basic overview
# for some common pfctl commands and is by no means
# a replacement for the pfctl and pf manual pages.

andresaquino

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

andresaquino

#!/usr/bin/env bash

# 
# Install:
#   cp iconresize.sh ~/bin/iconresize
#   chmod 0700 ~/bin/iconresize
#
# How to use:
#   iconresize <filename:icon.png> <directory:android> <tool:im|ff>
#