rande

assetic:
    debug:            false
    use_controller:   false
    read_from:        %kernel.root_dir%/../web
    write_to:         %kernel.root_dir%/../web
    dump_on_warmup:   false                     # do not compile on cache warmup
    bundles: []                                 # disable bundles parsing

    filters:
        yui_js:

beberlei

<?php
// tests/MyProject/Tests/DoctrineTestCase.php
namespace MyProject\Tests;

use Doctrine\ORM\Tools\SchemaTool;
use Doctrine\ORM\EntityManager;

class DoctrineTestCase extends \PHPUnit_Framework_TestCase
{
    protected $em;

jareware

⇐ back to the gist-blog at jrw.fi

Advanced SCSS

Or, 16 cool things you may not have known your stylesheets could do. I'd rather have kept it to a nice round number like 10, but they just kept coming. Sorry.

I've been using SCSS/SASS for most of my styling work since 2009, and I'm a huge fan of Compass (by the great @chriseppstein). It really helped many of us through the darkest cross-browser crap. Even though browsers are increasingly playing nice with CSS, another problem has become very topical: managing the complexity in stylesheets as our in-browser apps get larger and larger. SCSS is an indispensable tool for dealing with this.

This isn't an introduction to the language by a long shot; many things probably won't make sense unless you have some SCSS under your belt already. That said, if you're not yet comfy with the basics, check out the aweso

jbenet

a simple git branching model (written in 2013)

This is a very simple git workflow. It (and variants) is in use by many people. I settled on it after using it very effectively at Athena. GitHub does something similar; Zach Holman mentioned it in this talk.

Update: Woah, thanks for all the attention. Didn't expect this simple rant to get popular.

h4cc

# Install a Webserver
apt-get -y install apache2
# Target docroot to /home/satis/web/


# Install PHP5 CLI and needed programs.
apt-get -y install php5-cli php5-curl php5-json git wget

# Add a specifix user for our task
adduser satis

leesmith

Simple Git Workflow For Continuous Delivery

Workflow guidelines:

• master branch is always production-ready, deployable, 100% green test suite
• New development is done on feature branches, with frequent rebasing onto master
• Clean commit history by preferring to rebase instead of merge (git pull is configured to automatically rebase)

Workflow

paulirish

/* bling.js */

window.$ = document.querySelectorAll.bind(document);

Node.prototype.on = window.on = function (name, fn) {
  this.addEventListener(name, fn);
}

NodeList.prototype.__proto__ = Array.prototype;

lunetics

access.format = "[%{%Y-%m-%dT%H:%M:%S%z}t] requestid:%{REQUEST_ID}e frontendip:%R frontendhost:%{SERVER_HOSTNAME}e host:%{HTTP_HOST}e clientip:%{REAL_IP}e https:%{HTTPS}e verb:%m response:%s fpm_pool:%n request:\"%{REQUEST_URI}e%Q%q\" script_filename:%f php_process_time:%{micro}d php_process_bytes:%{bytes}M php_cpu_user:%{user}C%% php_cpu_system:%{system}C%% php_cpu_total:%{total}C%%"

HeahDude

<?php

// src/AppBundle/Twig/MacroTwigExtension.php

namespace AppBundle\Twig;

class MacroAutoloadTwigExtension extends \Twig_Extension
{
    public function getFunctions()
    {

nknapp

FROM traefik:camembert
ADD traefik.toml .
EXPOSE 80
EXPOSE 8080
EXPOSE 443