Jon Paul Uritis jppope

Things I believe

This is a collection of the things I believe about software development. I have worked for years building backend and data processing systems, so read the below within that context.

Agree? Disagree? Feel free to let me know at @JanStette.

Fundamentals

Keep it simple, stupid. You ain't gonna need it.

📝️ This document is part of several gists with Programming Quotes: • 5ffd57393a85553ab55b • 5cd28e2a812e5c65c9f7320e0726da18 • b6a6676a84b51c8200d0673a5b4a87c5

Programming Quotes

The quotes on this page come from this deleted question on Stackoverflow:

Howto Install clamav on OSX with brew

Note: on legacy intel system the path may be /usr/local/etc/clamav instead of /opt/homebrew/etc/clamav/

$ brew install clamav
$ cd /opt/homebrew/etc/clamav/
$ cp freshclam.conf.sample freshclam.conf

References:

https://github.com/tesseract-ocr/tesseract/wiki/Compiling

http://stackoverflow.com/questions/33588262/tesseract-ocr-on-aws-lambda-via-virtualenv

https://github.com/sirfz/tesserocr

Instructions for running Tesseract OCR on AWS Lambda with Python

Overview

This gist is intended for users who follow a forked repository/pull-request git workflow. Overtime, you may notice your forked repository's master branch becomes cluttered with "merged upstream/master into master"-type commits. These commits don't serve much of a purpose, and tend to clutter the commit history of any new pull requests you make.

By running the scripts below, we will delete your old master and create a new one based off of upstream/master. This will remove all of those unnecessary commits we don't want to see anymore. Based on the nature of how this works, you should be aware of a few things:

This method relies on a force push, and "erases" git history. This is a bad practice, especially when working on the same repository with other people, so make sure you understand the consequences of a force push before you do it.
Any work you have in your fork's master branch must have been merged to upstream/master or saved in another branch. If not, you will lose it all.
I

Get ClamAV running on Mac OS X (using Homebrew)

The easiest way to get the ClamAV package is using Homebrew

$ brew install clamav

Before trying to start the clamd process, you'll need a copy of the ClamAV databases.

Create a freshclam.conf file and configure as so

#Laravel 5 Simple ACL manager

Protect your routes with user roles. Simply add a 'role_id' to the User model, install the roles table and seed if you need some example roles to get going.

If the user has a 'Root' role, then they can perform any actions.

Installation

Simply copy the files across into the appropriate directories, and register the middleware in App\Http\Kernel.php

	/**
	* Encrypts plaintext using AES-GCM with supplied password, for decryption with aesGcmDecrypt().
	* (c) Chris Veness MIT Licence
	*
	* @param {String} plaintext - Plaintext to be encrypted.
	* @param {String} password - Password to use to encrypt plaintext.
	* @returns {String} Encrypted ciphertext.
	*
	* @example
	* const ciphertext = await aesGcmEncrypt('my secret text', 'pw');

	var AWS = require('aws-sdk'),
	fs = require('fs');

	// http://docs.aws.amazon.com/AWSJavaScriptSDK/guide/node-configuring.html#Credentials_from_Disk
	AWS.config.loadFromPath('./aws-config.json');

	// assume you already have the S3 Bucket created, and it is called ierg4210-shopxx-photos
	var photoBucket = new AWS.S3({params: {Bucket: 'ierg4210-shopxx-photos'}});

	function uploadToS3(file, destFileName, callback) {