chriseppstein

Sass/Less Comparison

In this document I am using Sass's SCSS syntax. You can choose to use the indented syntax in sass, if you prefer it, it has no functional differences from the SCSS syntax.

For Less, I'm using the JavaScript version because this is what they suggest on the website. The ruby version may be different.

Variables

beberlei

<?php

use Doctrine\ORM\EntityManager,
    Doctrine\ORM\Configuration,
    Doctrine\ORM\Mapping\ClassMetadata;

/**
 * Active Entity trait
 * 
 * Limitations: a class can only ever be assocaited with ONE active entity manager. Multiple entity managers

aarongustafson

iframe {
  max-width: 100%;
}

kikito

object(stdClass)#134 (16) {
  ["menu"]=>
  string(0) ""
  ["container"]=>
  bool(false)
  ["container_class"]=>
  string(0) ""
  ["container_id"]=>
  string(0) ""
  ["menu_class"]=>

xentek

WordPress Unit Tests Quick Start Guide

This quick start guide is geared towards installing PHPUnit on OSX in order to run the WordPress unit tests. It uses homebrew to install PHP using homebrew-php. You can likely skip this step if you've already got php and pear installed properly.

If you use MAMP, then try these instructions to use MAMP's php and pear to install PHPUnit.

install homebrew

ruby <(curl -fsSkL raw.github.com/mxcl/homebrew/go)

purwandi

set :application, "App Name"  # Your app name
set :repository,  "git@github.com:xxxxx/xxx.git"   # Your git repository

set :document_root, "/home/user/www/awesome_app"
set :deploy_via, :remote_cache

# SSH Settings
set :user, "user_ssh"
set :password, "password_ssh"
set :use_sudo, false

anchetaWern

There's no shortage of good resources for learning laravel. So instead of the usual introductory tutorial were just gonna learn Laravel by building a project from scratch and that's gonna be a User Management System.

I don't know if my definition of a User Management System is correct but here's my idea of what's it's capable of doing:

• Register Roles
• Register Users
• Update Users

jed

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

• Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.

• Use production SSL certificates locally. This is annoying

kevin-smets

Default

Powerlevel10k

brandonkelly

Templating in EE vs. Craft CMS.

Here are a few common tasks you might do in your templates, as they would be written in ExpressionEngine vs. Craft CMS.

Table of Contents

1. Comments
2. Conditionals
3. Loops
4. Looping Through Entries