ajcastro

Github: https://github.com/adoxa/ansicon
Copy paste ansicon folder to C:\.
Run in cmd:
  C:\ansicon> ansicon.exe -i

ajcastro

http://codeinthehole.com/writing/tips-for-using-a-git-pre-commit-hook/

Remember to chmod the .sh files for it to run.

Using php: http://carlosbuenosvinos.com/write-your-git-hooks-in-php-and-keep-them-under-git-control/

ajcastro

alias ..="cd .."
alias ...="cd ../.."
alias ll="ls -alF"
alias proj="cd d:\Projects"

#*****#
# Git #
#*****#
alias gp="git pull"
alias gs="git status"

ajcastro

<?php

class PThread extends Thread
{
    protected $id = ''; //ThreadID

    public function __construct($idThread)
    {
        $this->id = $idThread;
    }

ajcastro

# Instructions. Copy and paste the codes below:

cd /usr/local/src

# Download all needed archives, four(4) archives
# For PHP source
wget http://au1.php.net/get/php-5.6.21.tar.bz2/from/this/mirror -O php.tar.gz 
# For curl. You can choose from any mirror site from https://curl.haxx.se/latest.cgi?curl=tar.gz&all=yes
wget https://dl.uxnr.de/mirror/curl/curl-7.48.0.tar.gz 
# For libxml2

ajcastro

http://stackoverflow.com/questions/20560152/what-is-the-vagrant-syntax-for-adding-a-locally-existing-vdi http://stackoverflow.com/questions/26435510/how-to-copy-vagrant-box-to-reuse-again

Consider using command vagrant box repackage command, this is not tested, but there are links saying it is another way to package your box aside from the vagrant package command.

Create a metadata.json file inside the Homestead7 dir. (from the second link above, http://stackoverflow.com/a/39822306) This is something equivalent by renaming the folder name in /home/<user>/.vagrant.d/boxes/laravel-VAGRANTSLASH-homestead/

{
"name": "laravel/homestead",

ajcastro

# Source: http://askubuntu.com/questions/760671/could-not-load-vboxdrv-after-upgrade-to-ubuntu-16-04

# Follow instructions from 1 to 4 from the source url (stackoverflow).
# Then based from the comment also sign the following modules:`vboxnetflt`, `vboxnetadp`, and `vboxpci`. 
# After instruction 4: `sudo modprobe vboxdrv`, enter the following commands to finish signing the modules.

# Copy-paste the ff into the terminal:
sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vboxdrv)
sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vboxnetflt)
sudo /usr/src/linux-headers-$(uname -r)/scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vboxnetadp)

ajcastro

Sources for Git Workflow Tutorials
Recommended workflows: Gitlab-flow (when using gitlab) and Github-flow (when using github)

https://about.gitlab.com/2014/09/29/gitlab-flow/
http://scottchacon.com/2011/08/31/github-flow.html
http://nvie.com/posts/a-successful-git-branching-model/

https://guides.github.com/introduction/flow/
https://guides.github.com/activities/hello-world/
https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow

ajcastro

https://getcomposer.org/doc/04-schema.md#version
https://getcomposer.org/doc/articles/versions.md
http://qpleple.com/understand-composer-versions/

https://igor.io/2013/02/07/composer-stability-flags.html
http://webtips.krajee.com/setting-composer-minimum-stability-application/

ajcastro

https://phpunit.de/manual/current/en/code-coverage-analysis.html
https://jtreminio.com/2013/03/unit-testing-tutorial-introduction-to-phpunit/
http://code.tutsplus.com/tutorials/all-about-mocking-with-phpunit--net-27252