Laravel

SOLID principles

Coding, Design — Tags: Laravel, Thinking — Posted by Starck on October 1, 2013

The SOLID design principles, articulated by Robert “Uncle Bob” Martin, are five principles that provide a good foundation for sound application design. The five principles are:

S (Single Responsibility Principle)
O (Open/Closed Principle)
L (Liskov Substitution Principle)
I (Interface Segregation Principle)
D (Dependency Inversion Principle)

Single Responsibility Principle

A class (or unit of code) should have one responsibility.

設計一個類別，所有的實作應只為用來解決一個特定意圖（需求）而如果為了解決這個需求，而延伸出其它的需求與實作，應該把這些工作交給其它類別。

// MVC
class Controller {}
class Model {}
class View {}

// In this case, we want to validate something before storing it.
// Don't try to validate anything directly in Controller, Model or View ...etc. It will make them dirty.
// Just make Validation class and use it in those classes.
class Validation {}

// MVC

class Controller {}

class Model {}

class View {}

// In this case, we want to validate something before storing it.

// Don't try to validate anything directly in Controller, Model or View ...etc. It will make them dirty.

// Just make Validation class and use it in those classes.

class Validation {}

Open/Closed Principle

A class should be open for extension but closed for modification. You can extend a class or implement and interface, but you should not be able to modify a class directly. This means you should extend a class and use the new extension rather than change a class directly. Additionally, this means setting class attributes and methods as private or protected properly so they cannot be modified by external code.

一個類別應能被很有彈性地擴充，而不是直接修改其自身來解決新的意圖（需求）。以此原則來決定這個類別的屬性和方法該怎麼被限制，或該開放什麼？

ValidationModel

class ValidationModel {

    protected $rules;
    protected $messages;
    
    private $fields;
    private $validator;

    public function __construct( array $attributes = array() ) {
        $this->fields = $attributes;
    }

    public function passes() {
        
        $this->validator = Validator::make( $this->rules, $this->fields, $this->messages );
        if( $this->validator->isFail() ) {
            return $this->validator->messages()->first();
        }
        return true;

    }

}

class LoginValidationModel extends ValidationModel {
    protected $rules = array(
        'id'      => 'required|min:5',
        'password'    => 'required|min:8'
    );
    protected $messages = array(
        'id.required'     => 'ID is required for login.',
        'id.min'      => 'ID must be at least five characters.'
    );
}

class RegisterValidationModel extends ValidationModel {
    // ...
}

class ValidationModel {

protected $rules;

protected $messages;

private $fields;

private $validator;

public function __construct( array $attributes = array() ) {

$this->fields = $attributes;

}

public function passes() {

$this->validator = Validator::make( $this->rules, $this->fields, $this->messages );

if( $this->validator->isFail() ) {

return $this->validator->messages()->first();

}

return true;

}

class LoginValidationModel extends ValidationModel {

protected $rules = array(

'id' => 'required|min:5',

'password' => 'required|min:8'

);

protected $messages = array(

'id.required' => 'ID is required for login.',

'id.min' => 'ID must be at least five characters.'

);

}

class RegisterValidationModel extends ValidationModel {

// ...

}

Liskov Substitution Principle

Objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program. In PHP, this often means creating interfaces for your code to implement. You can then change (switch-out) implementations of the interfaces, Doing so should be possible without having to change how your application code interacts with the implementation. The interface serves as a contract, guaranteeing that certain methods will be available.

每當我們在一個類別引用了其它類別時，多思考如何往後如何切換或取代這件事，之後如果不用到它，會有什麼影響？如何讓更換這件事不費力？經驗上，我們往往會遇到一些被設計用來解決相同需求(購物這個需求)，但有各自實作方式(Paypal, Stripe …等支付方法)的情況，我們可以利用界面(interface)，定義一個大家共同遵循的規範(我們都應該有購買這個行為)，這個概念如同讓這些類別簽定了一個契約(Contract)，以確保都將一定會實行哪些行為。如此，我們只要專注那些行為在流程上的安排，不管現在這個實行的對象為何都不致於讓流程出錯，甚致隨時可以將其取代成別的也簽定契約的類別。

LiskovSubstitution

interface FileInterface {
    public function setName( $name = '' );
    public function getName();
    public function setDescription( $description = '' );
    public function getDescription();
}
interface DiskInterface {
    public function connect( ProtocolInterface $protocol );
    public function save( FileInterface $file );
}
interface ProtocolInterface {
    public function save( FileInterface $file );
}

class UsbProtocol implements ProtocolInterface {
    public function save( FileInterface $file) {
        $file->setDescription( $file->getName(). ' was saved via usb protocol.');
    }
}

class ThumderboltProtocol implements ProtocolInterface {
    public function save( FileInterface $file) {
        $file->setDescription( $file->getName(). ' was saved via thumderbolt protocol.');
    }
}

class Disk implements DiskInterface {
    protected $protocol;
    public function connect( ProtocolInterface $protocol ) {
        $this->protocol = $protocol;
    }
    public function save( FileInterface $file ) {
        $this->protocol->save( $file );
    }
}

class File implements FileInterface {
    protected $filename = 'undefined';
    protected $ext = '';
    protected $description = '';
    public function __construct() {
        $this->filename = $this->filename.$this->ext;
    }
    public function setName( $name = '' ) {
        $this->filename = $name . $this->ext;
    }
    public function getName() {
        return $this->filename;
    }
    public function setDescription( $description = '' ) {
        $this->description = $description;
    }
    public function getDescription() {
        return $this->description;
    }
}

class DocFile extends File {
    protected $ext = '.docx';
}
class ExcelFile extends File {
    protected $ext = '.xls';
}

$disk = new Disk();
$disk->connect( new ThumderboltProtocol );
$file  = new DocFile();
$disk->save( $file );

interface FileInterface {

public function setName( $name = '' );

public function getName();

public function setDescription( $description = '' );

public function getDescription();

}

interface DiskInterface {

public function connect( ProtocolInterface $protocol );

public function save( FileInterface $file );

}

interface ProtocolInterface {

public function save( FileInterface $file );

}

class UsbProtocol implements ProtocolInterface {

public function save( FileInterface $file) {

$file->setDescription( $file->getName(). ' was saved via usb protocol.');

}

class ThumderboltProtocol implements ProtocolInterface {

public function save( FileInterface $file) {

$file->setDescription( $file->getName(). ' was saved via thumderbolt protocol.');

}

class Disk implements DiskInterface {

protected $protocol;

public function connect( ProtocolInterface $protocol ) {

$this->protocol = $protocol;

}

public function save( FileInterface $file ) {

$this->protocol->save( $file );

}

class File implements FileInterface {

protected $filename = 'undefined';

protected $ext = '';

protected $description = '';

public function __construct() {

$this->filename = $this->filename.$this->ext;

}

public function setName( $name = '' ) {

$this->filename = $name . $this->ext;

}

public function getName() {

return $this->filename;

}

public function setDescription( $description = '' ) {

$this->description = $description;

}

public function getDescription() {

return $this->description;

}

class DocFile extends File {

protected $ext = '.docx';

}

class ExcelFile extends File {

protected $ext = '.xls';

}

$disk = new Disk();

$disk->connect( new ThumderboltProtocol );

$file = new DocFile();

$disk->save( $file );

Interface Segregation Principle

Many client-specific interfaces are better than one general-purpose interface. In general, it’s preferable to create an interface and implement it many times over than create a general-purpose class which attempts to work in all situations.

因為在程式語言中，一旦行為(method)在界面(interface)中被定義，在類別中就要嚴格地去實作。所以應該避免用一個很概廓性的界面讓類別去實作很多不必要的行為。就設計的角度來看，就是思考如何拆分行為的關連性這件事。

interface isFlyable() {
    public function fly();
}
interface isWalkable() {
    public function walk();
}
interface isSwimable() {
    public function swim();
}

class Starck implements isWalkable {
    public function walk() {}
}
class Pigeon implements isFlyable, isWalkable {
    public function fly() {}
    public function walk() {}
}
class Jessie implements isWalkable, isSwimable {
    public function walk() {}
    public function swim() {}
}

interface isFlyable() {

public function fly();

}

interface isWalkable() {

public function walk();

}

interface isSwimable() {

public function swim();

}

class Starck implements isWalkable {

public function walk() {}

}

class Pigeon implements isFlyable, isWalkable {

public function fly() {}

public function walk() {}

}

class Jessie implements isWalkable, isSwimable {

public function walk() {}

public function swim() {}

}

Dependency Inversion Principle

One should depend upon abstractions rather than concrete classes. You should define class dependencies as an interface rather than a concrete class. This allows you to switch an implementation of the interface out without having to change the class using the dependency.

This principle states that high-level code should not depend on low-level code, and that abstractions should not depend upon details.

依賴界面的關係比依賴類別來得更好，目的是希望在一個系統中元件之間相互依賴的程度（耦合性）盡可能的降低，以避免牽一髮動全身的情況發生。以這個原則來說，最常見的情況，就是該怎麼設計如何切換資料來源的機制。資料的存取可能是在 MySQL, NoSQL, 甚至是 Memory，我們如何在不影響主程式太多的情況下改變來源?

舉例來說

class DbMysql {
    public function getAll( $target ) { ... }
}
class Me {
  public fuunction getAllUsersFromMySql() {
      $db = new DbMysql;
      return $db->getAll('user');
  }
}
$me = new Me;
$me->getAllUsersFromMySql();

class DbMysql {

public function getAll( $target ) { ... }

}

class Me {

public fuunction getAllUsersFromMySql() {

$db = new DbMysql;

return $db->getAll('user');

}

$me = new Me;

$me->getAllUsersFromMySql();

這段程式大概是長得像這樣的句子：

「我要去MySQL檔案庫查詢使用者名單」。

這是一個耦合性高的句子，意即我們想要稍微改變一下行為，整個「」裡的文字都要變動，所以我們稍微調整一下：

我要去 MySQL 檔案庫「查詢使用者名單」。

MySQL 檔案庫為 來源地, 而 查詢使用者名單 為動作。

class DbMysql {
    public function getAll( $target ) { ... }
}
class Me {
  public fuunction getAllUsersFrom(DbMysql $db) {
      return $db->getAll('user');
  }
}
$me = new Me;
$me->getAllUsersFrom( new DbMysql );

class DbMysql {

public function getAll( $target ) { ... }

}

class Me {

public fuunction getAllUsersFrom(DbMysql $db) {

return $db->getAll('user');

}

$me = new Me;

$me->getAllUsersFrom( new DbMysql );

雖然我把來源地區隔開來，但實際上如果我改去 NoSQL 檔案庫，那麼這個句子還是會出錯，因為我們明確指出我們要到 MySql 檔案庫，該用什麼句子來表達才不會有問題呢？

答案是使用統稱：「我」要去「檔案庫」「查詢使用者名單」。

interface RepositoryInterface {
    public getAll( $target );
}
class MySqlRepository implements RepositoryInterface {
    public getAll( $target ) { ... }
}
class NoSqlRepository implements RepositoryInterface {
    public getAll( $target ) { ... }
}
class Me {
  public function getAllUsersFrom( RepositoryInterface $repository ) {
      return $repository->getAll('user');
  }
}
$me = new Me;
// MySql
$me->getAllUsersFrom( new MySqlRepository );
// NoSql
$me->getAllUsersFrom( new NoSqlRepository );

interface RepositoryInterface {

public getAll( $target );

}

class MySqlRepository implements RepositoryInterface {

public getAll( $target ) { ... }

}

class NoSqlRepository implements RepositoryInterface {

public getAll( $target ) { ... }

}

class Me {

public function getAllUsersFrom( RepositoryInterface $repository ) {

return $repository->getAll('user');

}

$me = new Me;

// MySql

$me->getAllUsersFrom( new MySqlRepository );

// NoSql

$me->getAllUsersFrom( new NoSqlRepository );

白話一點就是叫我們講話講得愈模糊愈好，就像是如果我跟一個以上的女朋友同時在交往，每一位打電話來我都叫她「親愛的」，這樣就可以避免叫錯人的情況啦。

interface UserInterface {
    public function all() {};
}

class EloquentUserRepository implements UserInterface {
    public function all() {
        return User::all()->toArray();
    }
}

class DbUserRepository implements UserInterface {
    public function all() {
        return DB::table('users')->get();
    }
}

class MemoryUserRepository implements UserInterface {
    public function all() {
        return Mem::key('users')->getAll();
    }
}

class BaseController { portected $users; }
class Controller extends BaseController {
    public function __construct( UserInterface $users ) {
        $this->users = $users;
    }
    public function getUsers() {
        $this->users->all();
    }
}

// get all users via Eloquent Model
$controller = new Controller( new EloquentUserRepository );
// get all users via Database Query Builder
$controller = new Controller( new DbUserRepository );
// get all users from memory
$controller = new Controller( new MemoryUserRepository );

// in laravel, you can use App::bind for switching dependencies at runtime
App::bind( 'UserInterface', function() {
    return new EloquentUserRepository( ... );
});

interface UserInterface {

public function all() {};

}

class EloquentUserRepository implements UserInterface {

public function all() {

return User::all()->toArray();

}

class DbUserRepository implements UserInterface {

public function all() {

return DB::table('users')->get();

}

class MemoryUserRepository implements UserInterface {

public function all() {

return Mem::key('users')->getAll();

}

class BaseController { portected $users; }

class Controller extends BaseController {

public function __construct( UserInterface $users ) {

$this->users = $users;

}

public function getUsers() {

$this->users->all();

}

// get all users via Eloquent Model

$controller = new Controller( new EloquentUserRepository );

// get all users via Database Query Builder

$controller = new Controller( new DbUserRepository );

// get all users from memory

$controller = new Controller( new MemoryUserRepository );

// in laravel, you can use App::bind for switching dependencies at runtime

App::bind( 'UserInterface', function() {

return new EloquentUserRepository( ... );

});

interface PaymentInterface {
    public function checkout();
}

interface PaymentPaypalInterface extends PaymentInterface {};
interface PaymentStripeInterface extends PaymentInterface {};


class PaymentController extends BaseController {
    protected $payment;
}

class PaypalPaymentController extends PaymentController {

    public function __construct( PaymentPaypalInterface $payment) {
        $this->payment = $payment;
    }
}

class StripPaymentController extends PaymentController {

    public function __construct( PaymentStripeInterface $payment) {
        $this->payment = $payment;
    }

}

class DynPaymentController extends PaymentController {
    public function __construct( PaymentInterface $payment ) {
        $this->payment = $payment;
    }
}

class PaypalPayment implements PaymentInterface {
    public $name = 'paypal';
    public function checkout() { return 'paypal checkout'; }
}
class StripePayment implements PaymentInterface {
    public $name = 'stripe';
    public function checkout() { return 'stripe checkout'; }
}

App::bind('PaypalRepository', 'PaypalPayment');
App::bind('StripeRepository', 'StripePayment');

App::bind('PaymentPaypalInterface', function() {

    // ...
    return new PaypalRepository();

});

App::bind('PaymentStripeInterface', function() {

    // ...
    return new StripeRepository();

});

App::bind('PaymentInterface', function() {

    $user = User::find(1);

    if( $user->payment == 'paypal' ) {

        return App::make('PaymentPaypalInterface');

    }else{

        return App::make('PaymentStripeInterface');

    }

});

interface PaymentInterface {

public function checkout();

}

interface PaymentPaypalInterface extends PaymentInterface {};

interface PaymentStripeInterface extends PaymentInterface {};

class PaymentController extends BaseController {

protected $payment;

}

class PaypalPaymentController extends PaymentController {

public function __construct( PaymentPaypalInterface $payment) {

$this->payment = $payment;

}

class StripPaymentController extends PaymentController {

public function __construct( PaymentStripeInterface $payment) {

$this->payment = $payment;

}

class DynPaymentController extends PaymentController {

public function __construct( PaymentInterface $payment ) {

$this->payment = $payment;

}

class PaypalPayment implements PaymentInterface {

public $name = 'paypal';

public function checkout() { return 'paypal checkout'; }

}

class StripePayment implements PaymentInterface {

public $name = 'stripe';

public function checkout() { return 'stripe checkout'; }

}

App::bind('PaypalRepository', 'PaypalPayment');

App::bind('StripeRepository', 'StripePayment');

App::bind('PaymentPaypalInterface', function() {

// ...

return new PaypalRepository();

});

App::bind('PaymentStripeInterface', function() {

// ...

return new StripeRepository();

});

App::bind('PaymentInterface', function() {

$user = User::find(1);

if( $user->payment == 'paypal' ) {

return App::make('PaymentPaypalInterface');

}else{

return App::make('PaymentStripeInterface');

}

});

<?php namespace Database;

class Database
{
    protected $adapter;

    public function __construct(AdapterInterface $adapter)
    {
        $this->adapter = $adapter;
    }
}

interface AdapterInterface {}
 
class MysqlAdapter implements AdapterInterface {}

<?php namespace Database;

class Database

{

protected $adapter;

public function __construct(AdapterInterface $adapter)

{

$this->adapter = $adapter;

}

interface AdapterInterface {}

class MysqlAdapter implements AdapterInterface {}

Comments (0)

Log Review #1 ( Tutorial HTML CSS jQuery Laravel AngularJS)

Log — Tags: AngularJS, Bootstrap, Chrome, CSS, Diff, jQuery, Laravel, PHP, transition — Posted by Starck on August 27, 2013

PHP

Class – PHP Fine Diff

AngularJS

Github – AngularJS Book (Chinese Language)

HTML / CSS

Tutorial – CSS-Tricks : CSS3 transition
Tutorial – CSS Vertical Align Center
Tool – Chrome DevTool : Workspace
- Setting
- Coding on workspace of Chrome Developer tools
Tutorial – Bootstrap 3 Grid Introduction
Theme – Bootstrap Theme from bootstrapmaster.com
Tutorial – An Advanced Guide to HTML & CSS

jQuery / JavaScript

Interface – DropKick : Styling <Select> input
- Tutorial – How to style selects using DropKick
- Github – DropKick

Comments (0)

Modern Testing with Laravel 4

Coding, Log — Tags: Laravel, PHP, Thinking — Posted by Starck on June 18, 2013

Behavior-Driven Development

簡稱 BDD, 簡單地說就是用一種情境設定的方式來進行開發的過程。

在 Laravel 4 我們需要以下三種組合之一:

Codeception
[email protected] and Mink – (optional)
Selenium2, PhantomJS and Mink – (optional)

Codeception Installation

# 下載 codecept
$ wget http://codeception.com/codecept.phar
# 初始化 codecept, 它會建立所需的檔案在目前的目錄中的 tests 資料夾
$ php codecept.phar bootstrap

查看有什麼指令可以使用:

php codecept.phar

修改 tests/functional.suite.yml:

class_name: TestGuy
modules:
    enabled: [Laravel4, TestHelper]

class_name: TestGuy

modules:

enabled: [Laravel4, TestHelper]

因為我們新增了一個 Laravel4 的 module, 所以讓 Codeception 再次重新建立所需的 Class:

php codecept.phar build

Codeception Usage

建立第一個測試:

php codecept.phar generate:cept acceptance Fisrt

Codeception 會在 tests/acceptance/ 下建立一個 FirstCept.php 檔案

內容為:

<?php
$I = new WebGuy($scenario);

1 2	<?php $I = new WebGuy($scenario);

First Scenario

我要到 / (網站首頁)。
我看到了 Hello World! 這段文字出現在首頁上。

這樣的情境，寫成測試檔就變成如下:

<?php
$I = new WebGuy($scenario);
$I->wantTo('goto homepage, and see hello word');
$I->amOnPage('/');
$I->see('Hello World!');

<?php

$I = new WebGuy($scenario);

$I->wantTo('goto homepage, and see hello word');

$I->amOnPage('/');

$I->see('Hello World!');

執行測試:

php codecept.phar run

Zombie.JS and Mink

由於 Codeception 的 PhpBrowser 是基於 PHP Curl 去實現模擬 Browser 的操作, 所以面對一些會有 Javascript 互動的網頁，在測試上就會顯得力不從心。還好 Codeception 提供了 ZombieJS module, 我們可以得到一個更真實的模擬測試。

Zombie.JS

Zombie.JS 是一個 NPM 的 package, 所以在這之前我們必須先安裝好 NPM 的環境。

將 zombie 1.4.1 版安裝到全域環境:

sudo npm install -g [email protected]

2013-06-18 註: 經測試, 目前只能裝 1.4.1 的版本, 版本太新 Mink 不支援.

開啟 ~/.bashrc, 加上 NODE_PATH 的設定

export NODE_PATH="/usr/local/lib/node_modules"

Mink

在 composer.json 中加入到 require:

"behat/mink": "1.5.*@dev"

重新更新 composer:

composer update

目前已知問題： checkOption(), uncheckOption(), executeJs() 無作用

Selenium2 and PhantomJS

比起 Zombie.JS, 我更喜歡 PhantomJS, 更穩定且資源豐富. 主要看到官方的一些範例, 真得相當地強大, 甚至可以 Screenshot… (Codeception 用來當發生測試失敗時會將快照存在 log 資料夾, 相當地方便!)

要使用 PhantomJS 當作 Browser, 我們需要 Selenium2 作 driver.

先執行 Selenium2:

java -jar selenium-server-standalone-2.33.0.jar

將會啟動一個 Selenium2 Server, 預設會使用 port 4444, 如需修改可在後面加上 -port 參數:

java -jar selenium-server-standalone-2.33.0.jar -port 8888

08:17:34.571 INFO - Java: Apple Inc. 20.45-b01-451
08:17:34.572 INFO - OS: Mac OS X 10.7.5 x86_64
08:17:34.584 INFO - v2.33.0, with Core v2.33.0. Built from revision 4e90c97
08:17:34.691 INFO - RemoteWebDriver instances should connect to: http://127.0.0.1:4444/wd/hub
08:17:34.692 INFO - Version Jetty/5.1.x
08:17:34.692 INFO - Started HttpContext[/selenium-server/driver,/selenium-server/driver]
08:17:34.693 INFO - Started HttpContext[/selenium-server,/selenium-server]
08:17:34.693 INFO - Started HttpContext[/,/]
08:17:34.738 INFO - Started org.openqa.jetty.jetty.servlet.ServletHandler@56d73c7a
08:17:34.738 INFO - Started HttpContext[/wd,/wd]
08:17:34.746 INFO - Started SocketListener on 0.0.0.0:4444
08:17:34.746 INFO - Started org.openqa.jetty.jetty.Server@54cbf30e

接著啟動 PhantomJS 跟 Selenium2 連接:

phantomjs --webdriver=4444

PhantomJS is launching GhostDriver...
[INFO  - 2013-06-18T00:17:27.627Z] GhostDriver - Main - running on port 4444

然後設定 Codeception 的 tests/acceptance.suite.yml 設定檔, 指定用 Selenium2 module:

modules:
   enabled: [Selenium2]
   config:
      Selenium2:
         url: 'http://starck-macmini'
         browser: firefox
         capabilities:
             unexpectedAlertBehaviour: 'accept'
             # delay: 500

modules:

enabled: [Selenium2]

config:

Selenium2:

url: 'http://starck-macmini'

browser: firefox

capabilities:

unexpectedAlertBehaviour: 'accept'

# delay: 500

url (required) – start url for your app
browser (required) – browser that would be launched
host – Selenium server host (localhost by default)
port – Selenium server port (4444 by default)
delay – To set delay between actions in milliseconds (1/1000 of second) if they run too fast
capabilities – To set Selenium2 desired capabilities. Should be a key-value array.

Comments (0)

Laravel 4 – Resources

Coding — Tags: Laravel, PHP — Posted by Starck on June 14, 2013

Starter

Package

IDE helper

Comments (1)

Laravel – Inject inline content into a section.

Coding — Tags: Laravel, PHP — Posted by Starck on June 7, 2013

手動注入 section 內容:

$view = View::make('layouts.scaffold');
$view->getEnvironment()->inject('main',$return);

1 2	$view = View::make('layouts.scaffold'); $view->getEnvironment()->inject('main',$return);

layouts/scaffold.blade.php:

<!doctype html>
<html>
    <head>
        <meta charset="utf-8">
        <title>Scaffold</title>
        <link href="//netdna.bootstrapcdn.com/twitter-bootstrap/2.3.1/css/bootstrap-combined.min.css" rel="stylesheet">
        <style>
            table form { margin-bottom: 0; }
            form ul { margin-left: 0; list-style: none; }
            .error { color: red; font-style: italic; }
            body { padding-top: 20px; }
        </style>
    </head>

    <body>

        <div class="container">
            @if (Session::has('message'))
                <div class="flash alert">
                    {{ Session::get('message') }}
                </div>
            @endif

            @yield('main')
        </div>

    </body>

</html>

<!doctype html>

<html>

<head>

<title>Scaffold</title>

<style>

table form { margin-bottom: 0; }

form ul { margin-left: 0; list-style: none; }

.error { color: red; font-style: italic; }

body { padding-top: 20px; }

</style>

</head>

<body>

@if (Session::has('message'))

</div>

@endif

@yield('main')

</div>

</body>

</html>

Comments (0)

Laravel with Gmail

Coding — Tags: Laravel, PHP — Posted by Starck on June 6, 2013

修改 app/config/mail.php:

host 為 smtp.gmail.com
port 為 465
encryption 為 ssl

<?php

return array(

    'driver' => 'smtp',
    'host' => 'smtp.gmail.com',
    'port' => 465,
    'encryption' => 'ssl',

);

<?php

return array(

'driver' => 'smtp',

'host' => 'smtp.gmail.com',

'port' => 465,

'encryption' => 'ssl',

);

Test:

Route::get('/MailTest', function()
{
    $data['name'] = 'Starck Lin';
    Mail::send('emails.welcome', $data, function($message)
    {
        $message->to('xxx@xxx.com')->subject('Welcome!!!');
    });
});

Route::get('/MailTest', function()

{

$data['name'] = 'Starck Lin';

Mail::send('emails.welcome', $data, function($message)

{

$message->to('[email protected]')->subject('Welcome!!!');

});

Comments (1)

Laravel 4 Tutorial Part 2 – Migrations and Artisan

Log — Tags: Laravel, PHP — Posted by Starck on March 31, 2013

Migrations

Migrations Installation

migrate:install : it will crate a migrations table for record any changes of database.

$ php artisan migrate:install

1	$ php artisan migrate:install

Making a new migration record

migrate:make (create|remove)_tablename_table

$ php artisan migrate:make create_authors_table

1	$ php artisan migrate:make create_authors_table

The --table and --create options may also be used to indicate the name of the table, and whether the migration will be creating a new table:

$ php artisan migrate:make create_authors_table --table=authors --create

// up() 
Schema::create('authors', function($table){ 
  $table->increments('id'); 
  $table->string('name'); 
  $table->text('bio'); 
  $table->timestamp(); 
});

// down() 
Schema::drop('authors');

// up()

Schema::create('authors', function($table){

$table->increments('id');

$table->string('name');

$table->text('bio');

$table->timestamp();

});

// down()

Schema::drop('authors');

Running All Outstanding Migrations

$ php artisan migrate

To seed your database, you may use the db:seed command on the Artisan CLI:

$ php artisan db:seed

Rollback all migrations and run them all again

$ php artisan migrate:refresh --seed

Artisan

Check routes status: $ php artisan routes

Clear auto-load files: $ php artisan clear-compiled

Re-generate auto-load files: $ php artisan dump-autoload

Comments (0)

Laravel 4 Tutorial Part 1 – Installation and Configuration

Coding — Tags: Laravel, PHP — Posted by Starck on March 26, 2013

Laravel

根據官網的說法:

Laravel is a clean and classy framework for PHP web development. Freeing you from spaghetti code, Laravel helps you create wonderful applications using simple, expressive syntax.

Development should be a creative experience that you enjoy, not something that is painful. Enjoy the fresh air.

–

大略看了文件後，覺得跟 Ruby on Rails 的概念很接近，以下幾點特色很吸引我:

Artisan : command-line 的操作方式, 支持擴充指令
Autoloading : 採用 Composer 的 autoload 機制, 不用再一直忘了 require 了
Blade Template Engine : 簡單好用的模版引擎
Migration / Seeding : 資料庫的版本管理
Query Builder : 幾乎所有的 MVC Framework 都會有這樣的 SQL 操作類
Eloquent ORM / Auth : 直接就有 ORM 可以用! 並有一個簡單的 Authentication 機制
Dependency Injection
IoC Container

–

安裝

Get Laravel from Github

$ mkdir {project_folder}
$ cd {project_folder}
$ get clone git://github.com/laravel/laravel.git
$ git checkout develop

–

Laravel 從 4 開始就不再用舊有的 Bundle, 而採用 Composer 來作 packages 的管理與安裝.

下載 Composer

$ curl -sS https://getcomposer.org/installer | php

付予 Composer 可執行的權限

這時專案資料夾會有一個 composer.phar 的文件, 我習慣把它命名為 composer 並付予可執行的權限:

$ chmod +x ./composer.phar
$ mv composer.phar composer

–

安裝 Composer

$ composer install

安裝 Laravel 所需的 packages

$ composer update

到這裡如果都沒有發生任何錯誤, Laravel 4 就算安裝完成了.

–

開發工具

我個人偏好用 SublimeText 2 or Vim 來作為我開發的 IDE, 而基於 Laravel 我比較建議用 SublimeText, 因為有一個方便的 LaravelGenerator, 使用這個 Plugin 前需要安裝 Laravel-4-Generators.

安裝 LaravelGenerator SublimeText Plugin

在 SublimeText 中:

Command + Shift + p

出現提示後然後輸入:

install 選擇 Package Control: Install Package

接著輸入: LaravelGenerator 選擇我們要安裝的 Plugin

這樣我們就已經把 LaravelGenerator Plugin 裝進 SublimeText 了

–

安裝 Laravel-4-Generators Package

開啟專案根目錄下的 composer.json, 在 require 設定加入 "way/generators": "dev-master"

"require": {
    "laravel/framework": "4.0.*",
    "way/generators": "dev-master"
},

"require": {

"laravel/framework": "4.0.*",

"way/generators": "dev-master"

更新並下載所需的 packages

$ composer update

加入 Laravel 的 ServiceProvider

開啟 app/config/app.php

在 providers 中加上 'Way\Generators\GeneratorsServiceProvider', 讓 artisan 運行時自動載入所需的類別

檢查 Laravel-4-Generators 是否安裝成功

$ php artisan

如果出現訊息有包含以下資訊就代表 package 安裝成功了:

generate
  generate:migration   Generate a new migration.
  generate:model       Generate an Eloquent model.
  generate:resource    Generate a new resource.
  generate:seed        Generate a DB seed class.
  generate:test        Generate a PHPUnit Test.
  generate:view        Generate a new view

generate

generate:migration Generate a new migration.

generate:model Generate an Eloquent model.

generate:resource Generate a new resource.

generate:seed Generate a DB seed class.

generate:test Generate a PHPUnit Test.

generate:view Generate a new view

可以參考 Pro Workflow in Laravel and Sublime Text 中的影片教學.

–

設定

儲存區目錄權限設定

將 app/storage 這個資料夾裡所有文件和目錄都設為可寫入的權限:

$ chmod -R 777 ./app/storage/

在 Server 上因為我習慣上會把網站文件的群組設為 apache (CentOS) or www-data (Ubuntu), 再付予群組的寫入權限.

$ chown -R user:group ./app/storage
$ chmod -R g+x ./app/storage

環境設定

Laravel 的設定檔都統一放置在 app/config/ 裡, 而 Laravel 可以依據 HTTP host 來決定讀取不同的設定檔, 例如測試主機和正式主機的資料庫設定可能會有所不同.

設定檔預設就是用在 production 環境, 如果有特定的設定需要在 localhost 本機環境下作變動, 只要在 app/config/ 建立一個 local 資料夾, 並把設定檔放置其中即可, 例如 database.php.

example:

app/config/ - 放置正式上線的 production 設定
app/config/local/ - 放置本機環境的設定
app/config/testing/ - Unit Testing 用的設定

環境的定義請見 /bootstrap/start.php 中

/*
|--------------------------------------------------------------------------
| Detect The Application Environment
|--------------------------------------------------------------------------
|
| Laravel takes a dead simple approach to your application environments
| so you can just specify a machine name or HTTP host that matches a
| given environment, then we will automatically detect it for you.
|
*/

$env = $app->detectEnvironment(array(

    'local' => array('your-machine-name'),

));

|--------------------------------------------------------------------------

| Detect The Application Environment

|--------------------------------------------------------------------------

| Laravel takes a dead simple approach to your application environments

| so you can just specify a machine name or HTTP host that matches a

| given environment, then we will automatically detect it for you.

$env = $app->detectEnvironment(array(

'local' => array('your-machine-name'),

));

Laravel 已經事先幫你定義好 local 的環境定義, 所以你只需把 your-machine-name 置換成你的電腦名稱或是 localhost.

Encryption Key

在編寫任何程式之前, 請先修改 app/config/app.php 的 key (Encryption Key).

你也可以用 artisan 自動產生一組隨機文字的 key, 在這之前需要先將原本的 key 刪除:

/*
|--------------------------------------------------------------------------
| Encryption Key
|--------------------------------------------------------------------------
|
| This key is used by the Illuminate encrypter service and should be set
| to a random, long string, otherwise these encrypted values will not
| be safe. Make sure to change it before deploying any application!
|
*/

    'key' => '',

|--------------------------------------------------------------------------

| Encryption Key

|--------------------------------------------------------------------------

| This key is used by the Illuminate encrypter service and should be set

| to a random, long string, otherwise these encrypted values will not

| be safe. Make sure to change it before deploying any application!

'key' => '',

接著在 Terminal 下達:

$ php artisan key:generate

–

Comments (0)