Maksim Surguy msurguy

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

Sublime Text 2 – Useful Shortcuts (Mac OS X)

General

⌘T	go to file
⌘⌃P	go to project
⌘R	go to methods
⌃G	go to line
⌘KB	toggle side bar
⌘⇧P	command prompt

Update May 2017

Eric Bidelman has documented some of the common workflows possible with headless Chrome over in https://developers.google.com/web/updates/2017/04/headless-chrome.

Update

If you're looking at this in 2016 and beyond, I strongly recommend investigating real headless Chrome: https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md

Windows and Mac users might find using Justin Ribeiro's Docker setup useful here while full support for these platforms is being worked out.

Image processing:

http://intervention.olivervogel.net/image/

Oauth :

bitbucket.org/atticmedia/anvard

Payments integration

Balanced payments : https://github.com/balanced/balanced-php
Omnipay : https://github.com/adrianmacneil/omnipay

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

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

	var require = function (file, cwd) {
	var resolved = require.resolve(file, cwd \|\| '/');
	var mod = require.modules[resolved];
	if (!mod) throw new Error(
	'Failed to resolve module ' + file + ', tried ' + resolved
	);
	var cached = require.cache[resolved];
	var res = cached? cached.exports : mod();
	return res;
	};

	$('#overlay-objet img').droppable({
	tolerance: 'pointer',
	drop: _.bind(function(event, ui) {
	object = $(event.target);
	if (object.attr("data-val") != undefined){
	objectDrag = object.attr('data-val').toString();
	objectDrop = $(ui.draggable).attr('data-val').toString();
	//$(ui.draggable).removeClass('objet-drag').addClass('objet-hover');
	object.addClass('hidden');
	$('#'+object.attr('data-toggle')).removeClass('hidden');

	CREATE TABLE `makers` (
	`id` int(10) unsigned NOT NULL,
	`name` varchar(255) NOT NULL,
	`description` varchar(255) NOT NULL,
	`created_at` datetime NOT NULL,
	`updated_at` datetime NOT NULL,
	PRIMARY KEY (`id`)
	) ENGINE=InnoDB DEFAULT CHARSET=latin1;

	--

	<?php
	/**
	* An helper file for Laravel 4, to provide autocomplete information to your IDE
	* Generated with https://github.com/barryvdh/laravel-ide-helper
	*
	* @author Barry vd. Heuvel <[email protected]>
	*/

	// This is now merged with: https://gist.github.com/barryvdh/5227822
	// The same format is used for phpStorm, netBeans and Sublime Text Codeintel!