GuillaumeDievart

input {
    file {
        type => "magento-exception"
        path => "/path/to/magento/www/var/log/exception.log"
        codec => multiline {
            pattern => "^%{TIMESTAMP_ISO8601}"
            negate => true
            what => previous
        }
    }

madrobby

var CreditCard = {
  CARDS: {
    Visa: /^4[0-9]{12}(?:[0-9]{3})?$/,
    MasterCard: /^5[1-5][0-9]{14}$/,
    DinersClub: /^3(?:0[0-5]|[68][0-9])[0-9]{11}$/,
    Amex: /^3[47][0-9]{13}$/,
    Discover: /^6(?:011|5[0-9]{2})[0-9]{12}$/
  },
  TEST_NUMBERS: $w('378282246310005 371449635398431 378734493671000 '+
    '30569309025904 38520000023237 6011111111111117 '+

ceckoslab

<?php
$mysqlCommandPath      = 'to be filled';
$mysqldumptCommandPath = 'to be filled';

$remoteDbUnsername = 'to be filled';
$remoteDbPassword  = 'to be filled';
$remotePort        = 'to be filled';
$remotHost         = 'to be filled';
$remoteDb          = 'to be filled';

dm1try

function elixir_version() {
  if [ -f "$PWD/mix.exs" ]; then
    echo "$ELIXIR_VERSION "
  fi
}

function ruby_version() {
  if [ -f "$PWD/Gemfile" ]; then
    echo "${RUBY_VERSION#*-} "
  fi

boredzo

man() {
	env \
		LESS_TERMCAP_md=$'\e[1;36m' \
		LESS_TERMCAP_me=$'\e[0m' \
		LESS_TERMCAP_se=$'\e[0m' \
		LESS_TERMCAP_so=$'\e[1;40;92m' \
		LESS_TERMCAP_ue=$'\e[0m' \
		LESS_TERMCAP_us=$'\e[1;32m' \
			man "$@"
}

grega

#!/bin/bash

machines=()

for machine in `VBoxManage list runningvms|cut -d" " -f 1`; do
  machines+=("$machine")
done

if [ ${#machines[@]} -eq 1 ]; then
  machinename=$(echo ${machines[@]} | cut -d'_' -f 1)

Vinai

<?php

/**
 * Simple Magento integration test PHPUnit bootstrap
 */

chdir(__DIR__ . '/../..');

$mageFile = 'htdocs/app/Mage.php';
umask(0);

Vinai

My beef with composer and Magento

Magento has recently merged an architecture proposal with the goal of removing non-composer modules.
At first this seems like a good idea, but I think there are some problems.

Community Bias

Magento listens to the community. That is a good thing.

greghgradwell

0. In the beginning, there was the middle...

You're jumping into a novel at about Chapter 6. And no, that's not because you missed the earlier chapters. I am only writing it now because it has finally become something worth recording (and hopefully reading). First, let me assure you that this is neither a theoretical exercise, nor a vague description of a "stealth" project. In short order you will be introduced to the current prototype that has already demonstrated many of the original project goals. And there will be plenty of pictures (please ignore the fact that this post has approximately 0 pictures 😬).

This project started out as somewhat of an experiment, or rather, it was a means to scratch an itch that had been bothering me for a few years:

What does it take to make an autopilot sufficiently reliable, affordable, and integratable enough to be extremely useful?

Or written as more of a challenge:

Can I create an autopilot that I could trust, afford, and would actually want t

greghgradwell

1. Hardware vs. Software

Software is great, but at some point it has to interact with hardware or it's useless. One of the pressing questions early on was how many of the hardware interfaces could be written in Elixir. For example, the first peripheral I wanted to test out was an IMU (inertial measurement unit). If I were working with Arduino, I would have a library already available, ready to plug and play.

Should I connect the IMU to an Arduino board, and then interface with the Arduino board using a serial protocol of my choice? Or does the extra hardware outweigh the benefits of ready-to-use software?

Since I was still very new to Elixir, I thought it would be interesting to replicate one of my previous projects that had utilized Arduino, in this case a 2-axis camera gimbal. Do I have pictures of the original? No. Did I take pictures of the Elixir version before I took it apart? Also no. So we'll have to use our imaginations. (Don't worry, I hear your boos and I agree)All I can offer i