Prerequisite: have Python3 and Pip3 installed

Quick answer: adjust $PATH so it has the path to the AWS executable.

1) Find where it installed AWS.  The guide says to use which python3 – but when I installed Python it installed it to my user, not the system. When you ran `pip3 install awscli –updgrade –user` it should have spit out something like this `… awscli in ./Library/Python/3.8/lib/python/site-packages (1.18.18)`.  The “./” indicated it is a local path, NOT the system path. You can confirm by checking `ls -la /Users/<insert_user_name>/Library/Python/3.8/bin/aws`

2) Edit  ~./bash_profile and add the path

export PATH=/Users/<insert_user_name>/Library/Python/3.8/bin:$PATH

3) Reload the profile

source .bash_profile

4) Test – aws –version should output

aws-cli/1.18.18 Python/3.8.2 Darwin/17.7.0 botocore/1.15.18

The post Installing AWS CLI on Mac first appeared on Levi Jackson.

This guide assumes you already have a composer.json file created, and you’re looking to add a new private repository to that.

Part 1: Bitbucket configuration

Composer is going to need access to your Bitbucket account in order to fetch the private git repo. An OAuth consumer can be used to give composer access.
– In Bitbucket, go to your “Bitbucket Settings” page https://bitbucket.org/account/user/<username>/

– Click “OAuth”

– Click the “Add consumer” button

– Fill in the name, description, callback URL (this can be anything – composer won’t use it but it is required by Bitbucket), select This is a private consumer, and select Repositories: Read for the permissions.

Part 2: Composer configuration

Using the Key and Secret from the OAuth consumer you created in part 1, you will need to add an auth.json file in composer’s home directory.

 vi ~/.composer/auth.json

{
    "bitbucket-oauth": {
        "bitbucket.org": {
            "consumer-key": "myKey",
            "consumer-secret": "mySecret"
        }
    }
}

Part 3: Configure composer.json

1) Add your private repository to the configuration so composer can look there for packages. The URL for the repo can be found in Bitbucket by clicking the “Clone” button in the top right of the repository view.

"repositories": [
  {
    "type": "git",
    "url": "https://aerosox@bitbucket.org/aerosox/dataconverter.git"
  }
]

2) Require the package in composer.json. With either of these methods.
– CLI: composer require aerosox/dataconverter
– Edit composer.json

"require": {
    "aerosox/dataconverter": "master@dev"
  }

Troubleshooting

1)  Ensure the package name in the require matches the name from the composer.json configuration for the package you are including.

// composer.json from aerosox/dataconvert

{
    // even though the git repo is configured as aerosox/dataconverter.git, this name *could* be anything. This is what composer is going to be looking for when it searches for the package to install.
    "name": "aerosox/dataconverter",
    "description": "Convert data formats",
    "type": "library",
    "authors": [
        {
            "name": "Levi Jackson",
            "email": "aerosox@gmail.com"
        }
    ],
    "autoload": {
        "psr-4": {
            "DataConverter\\": "src/"
        }
    },
    "require-dev": {
        "phpunit/phpunit": "^6.5"
    }
}

2) I saw a lot of guides say to load the package as “aerosox/dataconverter”: “master-dev”. I initially thought that master-dev was a composer standard, but it’s not. If you want to use that, you’d want to set up an alias in the package so it can be found.

"extra": {
  "branch-alias": {
    "dev-master": "actual-branch-name"
  }
}

The post Using a private repo with composer and bitbucket first appeared on Levi Jackson.

For all of these tests I set up the following beforehand:

ini_set('memory_limit', '500M');
$data = range(0, 1000000);

Test 1: array_filter vs loops

// array_filter loop average 0.74 seconds
$start = microtime(true);
$data = array_filter($data, function ($item) {
    return $item%2;
});
$end = microtime(true);

echo $end - $start;

// Foreach loop average 0.37 seconds
$start = microtime(true);
$newData = array();
foreach ($data as $item) {
    if ($item%2) {
        $newData[] = $item;
    }
}
$end = microtime(true);

echo $end - $start;

// For loop average 0.61 seconds
$start = microtime(true);
$newData = array();
$numItems = count($data);
for($i=0;$i<=$numItems;$i++) {
    if ($data[$i]%2) {
        $newData[] = $data[$i];
    }
}
$end = microtime(true);

echo $end - $start;

// While loop average 0.58 seconds
$start = microtime(true);
$newData = array();
$numItems = count($data);
$i = 0;
while ($i <= $numItems) {
    if ($data[$i]%2) {
        $newData[] = $data[$i];
    }
    $i++;
}
$end = microtime(true);

echo $end - $start;

Test 2: array_map vs loops

// array_map average 1.38 seconds
$start = microtime(true);
$data = array_map(function ($item) {
    return $item+1;
}, $data);
$end = microtime(true);

echo $end - $start;

// For loop average 0.65 seconds
$start = microtime(true);
$newData = array();
foreach ($data as $item) {
    $newData[] = $item+1;
}
$end = microtime(true);

echo $end - $start;

// For loop average 0.76 seconds
$start = microtime(true);
$newData = array();
$numItems = count($data);
for($i=0;$i<=$numItems;$i++) {
    $newData[] = $data[$i]+1;
}
$end = microtime(true);

echo $end - $start;

// While loop average 0.69 seconds
$start = microtime(true);
$newData = array();
$numItems = count($data);
$i = 0;
while ($i <= $numItems) {
    $newData[] = $data[$i];
    $i++;
}
$end = microtime(true);

echo $end - $start;

Test 3: array_walk vs loops

// array_walk average 0.72 seconds
$start = microtime(true);
$data = array_walk($data, function ($item) {
    return $item+1;
});
$end = microtime(true);

echo $end - $start;

// Foreach loop average 0.65 seconds
$start = microtime(true);
$newData = array();
foreach ($data as $item) {
    $newData[] = $item+1;
}
$end = microtime(true);

echo $end - $start;

// For loop average 0.76 seconds
$start = microtime(true);
$newData = array();
$numItems = count($data);
for($i=0;$i<=$numItems;$i++) {
    $newData[] = $data[$i]+1;
}
$end = microtime(true);

echo $end - $start;

// While loop average 0.69 seconds
$start = microtime(true);
$newData = array();
$numItems = count($data);
$i = 0;
while ($i <= $numItems) {
    $newData[] = $data[$i];
    $i++;
}
$end = microtime(true);

echo $end - $start;

End Notes

I was incorrect when I thought that array_* functions are faster! Albeit the speed difference is pretty negligible when talking about using it once or twice during page execution. I won’t stop using the array_* functions because of my findings, they still offer a cleaner way of writing the code. I will only second guess using them when I am writing code that has the potential to be processed thousands of times.

I tested these with a pretty basic data set. Speed may vary depending on the type of data being used as well as the version of PHP (I used 5.5.4).

The post Are array_* functions faster than loops? first appeared on Levi Jackson.

>> Uglifying source path/to/file.js failed.
Warning: Uglification failed.
Unexpected token punc «(», expected punc «:».
Line 12 in path/to/file.js
 Use --force to continue.

Aborted due to warnings.

When I went to line 12 I saw absolutely nothing wrong. It was a comment block like the following:

/*
An unobtrusive comment goes here
*/

I tried removing the file from the list being included and it happened again. Same error different file. Everything I was reading said it was most likely invalid Javascript doing it, but since I write code perfectly, that could not be the case. Fast forward 10-20 minutes and I found this issue on Github that sounded similar. A comment from Eric Range advised that their code editor had added a line ending of “\n\r” to the file and that caused their build to fail. So I took a look at line endings and sure enough, a handful of the files were using “\n\r”. I did a find/replace and changed them all to just a single new line (“\n”). I attempted to uglify it once more and yet again I was shown an error! I was beginning to think uglify and I were not going to be good friends.

Running "uglify:build" (uglify) task
{ message: 'Unexpected token: eof (undefined)',
  filename: 'file.js',
  line: 3032,
  col: 0,
  pos: 129381,
  stack: 'Error\n    at new JS_Parse_Error (/path/to/node/node_modules/grunt-contrib-uglify/node_modules/uglify-js/lib/parse.js:196:18)\n    at js_error (/path/to/nodenode_modules/grunt-contrib-uglify/node_modules/uglify-js/lib/parse.js:204:11)\n    at croak (/path/to/nodenode_modules/grunt-contrib-uglify/node_modules/uglify-js/lib/parse.js:678:41)\n    at token_error (/path/to/nodenode_modules/grunt-contrib-uglify/node_modules/uglify-js/lib/parse.js:682:9)\n    at unexpected (/path/to/nodenode_modules/grunt-contrib-uglify/node_modules/uglify-js/lib/parse.js:688:9)\n    at block_ (/path/to/nodenode_modules/grunt-contrib-uglify/node_modules/uglify-js/lib/parse.js:1000:28)\n    at /path/to/nodenode_modules/grunt-contrib-uglify/node_modules/uglify-js/lib/parse.js:974:25\n    at function_ (/path/to/nodenode_modules/grunt-contrib-uglify/node_modules/uglify-js/lib/parse.js:979:15)\n    at expr_atom (/path/to/nodenode_modules/grunt-contrib-uglify/node_modules/uglify-js/lib/parse.js:1187:24)\n    at maybe_unary (/path/to/nodenode_modules/grunt-contrib-uglify/node_modules/uglify-js/lib/parse.js:1357:19)' }
>> Uglifying source path/to/file.js failed.
Warning: Uglification failed.
Unexpected token: eof (undefined).
Line 3032 in path/to/file.js
 Use --force to continue.

Aborted due to warnings.

I looked at the differences between the files that worked and the ones that failed. The only difference I found was that the failed files used tabs instead of spaces (they were created at a time when there was no convention for tabs vs spaces). So I converted the files that were using tabs to spaces and tried again. Bingo! It worked perfect.

Final Solution

My final solution was to change all files to use unix line endings (“\n”) and to convert tabs to spaces.

The post GruntJS "Warning: Uglification failed." first appeared on Levi Jackson.

Given the following RequireJS config:

require.config({
    "baseUrl":"\/path\/to\/dir\/",
    "paths":{
        "jQuery":"jquery.js"
    }
});

I was trying to do the following:

require([jQuery], function ($) {
    console.log($);
});

That gave me the dreaded “jQuery not defined” error!

Solution

Add quotes around “jQuery”!

require(["jQuery"], function ($) {
    console.log($);
});

Without the quotes jQuery was being treated as a Javascript variable instead of a string. So when it was looking for the jQuery dependency it did not exist. “jQuery” on the other hand does.

The post RequireJS "jQuery not defined" first appeared on Levi Jackson.

 Iterators

There are a lot of iterators in PHP. Not all of them are part of the SPL though, such as SimpleXMLIterator, so keep that in mind as you may come across an iterator in places you may not expect. It can be pretty intimidating looking at the list, and it only gets worse when you see something called a RecursiveIteratorIterator.

ArrayIterator

ArrayIterator is probably going to be the best spot to start out. ArrayIterator bridges the gap between Array and Iterator and allows for conversion back and forth. In it’s most basic implementation it accepts an array as the parameter and it converts it into an iterator.

$cities = array('Torrington', 'Burlington', 'New York City', 'Warwick');
$cities = new ArrayIterator($cities);

/*
You can alternatively use these methods to add items to an ArrayIterator
$cities = new ArrayIterator();
$cities->append('Torrington');
$cities[] = 'Burlington';
$cities[] = 'New York City';
$cities->append('Warwick');
*/

The first thing you will realize is that the ArrayIterator has methods for some of the more common array functions such as asort, ksort, natsort, key, etc.. The second thing you will realize is that iterators do not have a 1:1 conversion in terms of array functions to iterator methods. So it may not be a suitable replacement for all instances where an array is currently used.

Chain Iterators Together

One great thing about iterators is the ability to chain them together. It opens up some pretty powerful capabilities such as filtering, merging items, and limiting output.  Some of it like limiting results, is exclusive to iterators, but other things like filtering can also be done using the array_ functions.

$cities = array('Torrington', 'Burlington', 'New York City', 'Warwick');
$cities = new ArrayIterator($cities);
$cities = new LimitIterator($cities, 0, 2);
foreach ($cities as $city) {
    echo $city;
}
// returns Torrington, Burlington

FilterIterator

FilterIterator is an abstract class that you can use to create custom filters to apply to the data in an iterator.

class CityFilter extends FilterIterator {
    protected $City;

    public function __construct(Iterator $iterator, $city) {
        parent::__construct($iterator);
        $this->City = $city;
    }

    public function accept() {
        return $this->current() == $this->City;
    }
}

$cities = array('Torrington', 'Burlington', 'New York City', 'Warwick');
$cities = new ArrayIterator($cities);
$cities = new CityFilter($cities, 'Burlington');

foreach ($cities as $city) {
    echo $city;
}
// returns Burlington

Merging Iterators

I mentioned earlier that you can merge iterators together. You do that with AppendIterator.

$cities1 = array('Torrington', 'Burlington');
$cities1 = new ArrayIterator($cities1);

$cities2 = array('New York City', 'Warwick');
$cities2 = new ArrayIterator($cities2);

$cities = new AppendIterator();
$cities->append($cities1);
$cities->append($cities2);

foreach ($cities as $city) {
    echo $city;
}
// returns Torrington, Burlington, New York City, Warwick

Converting an Iterator to an Array

So I showed you how to go from an array to an iterator. But what if you want to take your iterator and go back to an array if you need to use a function that is not available as a method? You have two options.

Option 1: ArrayIterator::getArrayCopy()

$cities = array('Torrington', 'Burlington', 'New York City', 'Warwick');
$cities = new ArrayIterator($cities);
$cities = $cities->getArrayCopy();

Option 2: iterator_to_array() function

$cities = array('Torrington', 'Burlington', 'New York City', 'Warwick');
$cities = new ArrayIterator($cities);
$cities = iterator_to_array($cities);

One difference between the two options is that ArrayIterator::getArrayCopy() will not execute chained iterators while iterator_to_array() will.

$cities = array('Torrington', 'Burlington', 'New York City', 'Warwick');
$cities = new ArrayIterator($cities);
$cities = new LimitIterator($cities, 0, 2);

$cities1 = iterator_to_array($cities);
print_r($cities1);
// returns Array ( [0] => Torrington [1] => Burlington )

$cities2 = $cities->getArrayCopy();
print_r($cities2);
// returns Array ( [0] => Torrington [1] => Burlington [2] => New York City [3] => Warwick )

 Closing

There are a lot more iterators I didn’t go over for you to explore, like the EmptyIterator in all its glory! I’m noticing one of the biggest advantages over array_ functions is the ease of reading the code. I can’t tell you how many times i’ve had to look at something that uses array_walk and array_map in the same variable and had to spend a few minutes working my way through what it does.

$something = array_walk(array_map(function(){
// some logic
}, $data) ,function() {
// some logic
});

An alternative to that might be to do:

$something = ArrayIterator($data);
$something = CallbackFilterIterator($something, function($current, $key, $iterator) {
// some logic
});

The post Working with iterators and arrays SPL first appeared on Levi Jackson.

I’m sure most of us have had to work with files in some manner. For me it usually takes the form of a logger or parser (CSV or XML). One of the things I have always thought would be helpful is an object to wrap the fopen, fwrite, fread, fclose functions so you didn’t need to maintain the file handle. Enter the SPL. It wraps a lot of the reading, writing, searching, and parsing into easy to use objects so that you don’t need to preserve that file handle in a variable.

SplFileInfo

SplFileInfo offers a way to get information about a file (as the name would suggest). Because it handles some of the more basic aspects of working with files, it won’t come as a shock that a lot of the other file related SPL objects extend SplFileInfo. Need to get the extension? Use SplFileInfo::getExtension(). How about the last modified time? SplFileInfo::getMTime(). Is the file a symbolic link to a different file? SplFileInfoisLink() to check and SplFileInfogetRealPath() to resolve to the actual location. The only thing it doesn’t do is handle reading and writing, but that is where SplFileInfo::openFile() comes into the picture. The openFile method will return an instance of SplFileObject that can be used to do reading/writing.

SplFileObject

SplFileObject inherits from SplFileInfo, so it has all of the same capabilities plus being able to read and write.

CSV Parsing

If you need to parse a CSV you can use the setFlags() method before parsing a file to set flags that will change how it handles parsing. SplFileObject::setFlags(SplFileObject::READ_CSV) sets the stage for parsing a csv file.  While on the topic of csv files… SplFileObject::setCsvControl() allows you to set the delimiter, enclosure, and escape character.

Reading Lines

To read the file line by line it’s as easy as using a loop.

foreach ($obj as $line) {
// SplFileObject::__toString() is set as an alias of SplFileObject::current(), which makes echo'ing the object return the current line.
echo $line;
}

DirectoryIterator

DirectoryIterator is used to list files and subdirectories. Like SplFileObject, it inherits from SplFileInfo. I’ll discuss iterators in another post, but for the sake of understanding the power of DirectoryIterator it is enough to know they are most often used in loops.

foreach (new DirectoryIterator('/path/to/dir') as $file) {
    echo $fileInfo->getFilename() . "\r\n";
}

This will yield something like:

.
..
filename.txt
directory
image.jpg

One useful method available in DirectoryIterator but not available in SplFileInfo is DirectoryIterator::isDot(). This returns true if the “file” is a “.” or “..” system file.

RecursiveDirectoryIterator

RecursiveDirectoryIterator is the recursive version of DirectoryIterator. It will go down into the subdirectories and list files and subdirectories and so on and so on.

$files = new RecursiveDirectoryIterator('/path/to/dir');
$files = new RecursiveIteratorIterator($files);
foreach ($files as $file) {
    echo $file . "\n\r";
}

This will yield something like:

.
..
filename.txt
directory
directory/file.txt
directory/subdirectory
directory/subdirectory/image.jpg
image.jpg

Closing

I only touched on some of the basic and useful parts of the SPL that I found to make working with files much easier and more logical. There is so much more for you and I to learn about them though.

The post Working with files and SPL first appeared on Levi Jackson.

1. Download and unzip/untar the Elasticsearch files http://www.elasticsearch.org/download
2. Download the latest version of Java (woo!)
3. Copy the directory to /usr/local: sudo mv elasticsearch /usr/local
4. To start it just execute: /usr/local/elasticsearch/bin/elasticsearch -f
5. To stop it, just hit command+c

Optional steps to allow you to start the service with just the ‘elasticsearch -f’ command:

1. Open your .bash_profile file for your bash profile settings
2. Add export ES_HOME=~/usr/local/elasticsearch/bin
3. Add export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home
4. Add export PATH=$ES_HOME/bin:$JAVA_HOME/bin:$PATH
5. Run ‘source ~/.bash_profile’ from terminal

The post Install Elasticsearch Mac OSX 10.9.1 first appeared on Levi Jackson.

Anyway, to get to the point. I was testing the importer from the browser and finding really inconsistent and perplexing things happening.

pcntl_wait and pcntl_waitpid not working

The code was setup to store an array of the pids used, and to not allow more than 10 child processes at a time. So it was supposed to hit pcntl_wait or pcntl_waitpid and clear out the pid that had finished.  The problem was that it never seemed to do that. I could see it was starting the processes and it was exiting them fine (ps -Hwfe from terminal verified there were no zombie processes).

My first thought after reading a bit about it was that perhaps the child process was finishing before the parent process had a chance to be informed the child process was starting. I tried adding sleep(10) into spots to try and delay the child process from finishing so quickly. Still didn’t work.

Solution

After realizing that pcntl_fork wasn’t supposed to be used from the browser when PHP was installed as an Apache module… I moved to using CLI to execute the script. I set it up so that I was using shell_exec() to execute the command after setting and uploading the import file. It worked great from CLI and I proceeded to bang my head into the wall a few times.

tldr; Use pcntl_fork, pcntl_wait, pcntl_waitpid in scripts run from CLI only… do not use them in the browser as that does not work as expected.

The post PHP pcntl_waitpid and pcntl_wait not working first appeared on Levi Jackson.

First step, pull it in (I used composer).

{
    "name" : "name of app",
    "description" : "Desc of app",
    "license" : "MIT",
    "require" : {
        "illuminate/database": "*"
    }
}

Setting up the database connection is relatively easy if you use the docs on the Github and Laravel as a guide.

$config = array(
    'db' => array(
        'driver' => 'mysql',
        'host' => '127.0.0.1',
        'database' => 'imdb',
        'username' => 'username',
        'password' => 'password',
        'collation' => 'utf8_general_ci',
        'charset' => 'utf8',
        'prefix' => 'imdb_',
        'port' => ''
    )
);

$connFactory = new \Illuminate\Database\Connectors\ConnectionFactory(new \Illuminate\Container\Container());
$conn = $connFactory->make($config['db']);
$resolver = new \Illuminate\Database\ConnectionResolver();
$resolver->addConnection('default', $conn);
$resolver->setDefaultConnection('default');
\Illuminate\Database\Eloquent\Model::setConnectionResolver($resolver);

Then all you really need to do is create your class file:

<?php
namespace ProjectName\Models;

use Illuminate\Database\Eloquent\Model;

class Movie extends Model {
    protected $fillable = array('title', 'release_date');
    protected $guarded = array('id', 'updated_at', 'created_at');
}

You can easily add a record to the database by doing:

$movie = new Movie(array('title' => A movie title, 'release_date' => '2014-01-23'));
$movie->save();

Nice and quick to get rolling so you aren’t spending so much time on the repetitive task of CRUD for each model.

The post Using Illuminate without Laravel first appeared on Levi Jackson.