The script below is triggered every day from my Mac. I use Hazel to move the tar.gz to an external hard disk once it's finished. This happens every day without me noticing. You can exclude folders if you want to. You probably want to exclude giant cache folders.
You should have a similar script.
=====
I made a book, its one page.
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>Responsive Design Testing</title> | |
| <style> | |
| body { margin: 20px; font-family: sans-serif; overflow-x: scroll; } | |
| .wrapper { width: 6000px; } | |
| .frame { float: left; } | |
| h2 { margin: 0 0 5px 0; } |
The [RFC for a new simple to use password hashing API][rfc] has just been accepted for PHP 5.5. As the RFC itself is rather technical and most of the sample codes are something you should not use, I want to give a very quick overview of the new API:
Everybody knows that you should be hashing their passwords using bcrypt, but still a surprising number of developers uses insecure md5 or sha1 hashes (just look at the recent password leaks). One of the reasons for this is that the crypt() API is ridiculously hard to use and very prone to programming mistakes.
| SMILE Plug is running: | |
| Linux SMILEplug 2.6.35.9-ARCH #7 PREEMPT Wed Sep 19 14:07:47 MDT 2012 armv7l GNU/Linux | |
| root@SMILEplug:~/spdist# cat /proc/cpuinfo | |
| Processor : Marvell PJ4Bv7 Processor�� rev 1 (v7l) | |
| BogoMIPS : 1199.30 | |
| Features : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16 | |
| CPU implementer : 0x56 | |
| CPU architecture: 7 | |
| CPU variant : 0x1 | |
| CPU part : 0x581 |
This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.
| [ | |
| { | |
| "keys": ["super+alt+left"], | |
| "command": "set_layout", | |
| "args": | |
| { | |
| "cols": [0.0, 0.33, 1.0], | |
| "rows": [0.0, 1.0], | |
| "cells": [[0, 0, 1, 1], [1, 0, 2, 1]] | |
| } |
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:
