jaywilliams

<?php
/**
 * Remove any non-ASCII characters and convert known non-ASCII characters 
 * to their ASCII equivalents, if possible.
 *
 * @param string $string 
 * @return string $string
 * @author Jay Williams <myd3.com>
 * @license MIT License
 * @link http://gist.github.com/119517

ziadoz

Awesome PHP

Awesome PHP has been relocated permanently to its own Github repository. No further updates will made to this gist.

Please open an issue for any new suggestions.

pamelafox-coursera

<?php

class CalendarEvent {

    /**
     * 
     * The event ID
     * @var string
     */
    private $uid;

ahmadazimi

<?php

/**
 * http://stackoverflow.com/questions/11305797/remove-zero-width-space-characters-from-a-javascript-string
 * U+200B zero width space
 * U+200C zero width non-joiner Unicode code point
 * U+200D zero width joiner Unicode code point
 * U+FEFF zero width no-break space Unicode code point
 */
 

ssx

input {
    lumberjack {
        port => 5000
        type => "logs"
        ssl_certificate => "/shared/logstash-certs/logstash-forwarder.crt"
        ssl_key => "/shared/logstash-certs/logstash-forwarder.key"
    }
}

## Add your filters here

damusix

Convert AWS IAM credentials to AWS SMTP credentials

If you do, or want to, use AWS to deploy your apps, you will end up using AWS SES via SMTP when you're launching an app that sends out emails of any kind (user registrations, email notifications, etc). For example, I have used this configuration on various Ruby on Rails apps, however, it is just basic SMTP configurations and crosses over to any framework that supports SMTP sendmail.

There are two ways to go about this:

• EASY WAY: Create an SMTP user via AWS SES [http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-credentials.html#smtp-credentials-console]
• NOT SO EASY WAY: Create an SMTP password for an existing IAM user [^^ Same link scroll down]

Luckily, you found this MD file and the NOT SO EASY WAY is suddenly copy-pasta... sudo yum....

tomazzaman

Killing supervisor if any of it's child processes fail

The trick is to only register the listener for events that indicate failure, namely

• PROCESS_STATE_STOPPED
• PROCESS_STATE_EXITED
• PROCESS_STATE_FATAL

Once they do, we should send a SIGQUIT to Supervisor.

efrecon

docker run \
  --name {{printf "%q" .Name}} \
    {{- with .HostConfig}}
        {{- if .Privileged}}
  --privileged \
        {{- end}}
        {{- if .AutoRemove}}
  --rm \
        {{- end}}
        {{- if .Runtime}}

calebporzio

<?php

function tinker(...$args) {
    // Because there is no way of knowing what variable names
    // the caller of this function used with the php run-time,
    // we have to get clever. My solution is to peek at the
    // stack trace, open up the file that called "tinker()"
    // and parse out any variable names, so I can load
    // them in the tinker shell and preserve their names.

fnky