從實例學設計模式 by jaceju

from : http://slides.com/jaceju/design-patterns-by-examples#/

phpstorm connection with xdebug was not established. validate installation

Another way to solve it - to change the port of xdebug in php.ini. For example to 9001:

xdebug.remote_port=9001

After that you need to change xdebug port in PhpStorm in Preferences->Languages & Frameworks -> PHP -> Debug. Xdebug port set to 9001.

from : http://stackoverflow.com/questions/31285486/connection-between-phpstorm-and-xdebug

Cannot tap homebrew/php: invalid syntax in tap!

Make sure you're not stuck behind the update bug as well.

cd $(brew --prefix) && git fetch && git reset --hard origin/master

from : https://github.com/Homebrew/homebrew-php/issues/3558

Mac OSX php7 curl error 35 fixed

I've seen this error happen when php is compiled with a version of cURL that uses Apple's Secure Transport under Yosemite and the target of the URL request doesn't support SSLv3 (which was probably disabled due to the POODLE vulnerability). What is the output of this command?

$ php -i | grep "SSL Version"

I suspect you'll see this:

SSL Version => SecureTransport

You can overcome this by installing a version of php which uses a version of cURL which uses OpenSSL instead of SecureTransport. This is most easily done with homebrew. So install that first if you don't already have it. If homebrew is installed but you haven't run brew update since upgrading to Yosemite, do that first. Also make sure you've installed XCode >= 6.1 and the latest XCode command line tools. brew doctor will tell you if you've done it all right.

Add the Homebrew taps below that you will need in order to get brewed php installed. Skip this step if these repos are already tapped. If you're unsure if these repos are already tapped, just run the commands below. Worst case scenario, you'll get a harmless Warning: Already tapped!

$ brew tap homebrew/dupes
$ brew tap homebrew/versions
$ brew tap homebrew/php

Then install curl with openssl:

$ brew install --with-openssl curl

Then install php using the curl you just installed and brewed openssl:

$ brew install --with-homebrew-curl php55

• if using apache, make sure to add LoadModule php5_module /usr/local/opt/php55/libexec/apache2/libphp5.so to your /etc/apache2/httpd.confand restart apache.
• if using nginx, follow the caveat instuctions for starting fpm:

  To launch php-fpm on startup:

  mkdir -p ~/Library/LaunchAgents
  cp /usr/local/opt/php55/homebrew.mxcl.php55.plist ~/Library/LaunchAgents/
  launchctl load -w ~/Library/LaunchAgents/homebrew.mxcl.php55.plist

Install any php extensions you're going to need eg. mcrypt.

$ brew install php55-mcrypt

After you're done, run this again:

$ php -i | grep "SSL Version"

And you should see:

SSL Version => OpenSSL/1.0.2h

And now, re-test your application

from : http://stackoverflow.com/questions/26461966/osx-10-10-curl-post-to-https-url-gives-sslread-error

Laracasts Tips

Request::exists('popular')
?popular  => true
?nopopular => false

Request::has('popular')
?popular => false
?popular=hasValue => true

Filter Model
$lesson = (new Lesson)->newQuery();
if($request->exists('popular')){
    $lesson->orderBy('views','desc');
}

if($request->has('difficulty')){
    $lesson->where('difficulty', $request->difficulty);
}

return $lesson->get();

Simpler Code
1. No Abbreviations
2. Don't use else
    - Defensive code
    - Guard
    - Reflection
3. One Level of Indentation
4. Limit you instance variables
    - One responsibility for one class ( No more that 4 instance variables)
5. Wrap  Primitives
    - Doest it bring clarity
    - Is there behavior?
      class EmailAdress {
          public function __construct($email){
              if ( ! filter_var($email, FILTER_VALIDATE_EMAIL)){
                  throw new InvalidArgumentException;
              }
              $this->email = $email;
          }
      }
    - Consistency
    - Important domain concept
      class Location {
          public function __construct($latitude, $longtitude){
          }
      }

Laravel Tips

Pretend login user
Auth::loginUsingId(x);

Hook event in Model
Class Document extend Eloquent
{
    public static functio boot(){
        parent::boot();
        static::updating(function($document)){
            //do something
        }
    }
}

Pivot Model method withTimestamps and withPivot
public function adjustments(){
    return $this->belongWithMany(User::class, 'adjustments')
                      ->withTimestamps()
                      ->withPivot(['before','after'])
                      ->latest('pivot_updated_at']);
}

Laravel 5 Dynamically create Eloquent Models

php

namespace App\Models;

use Illuminate\Database\Eloquent\Model;
use Sofa\Revisionable\Laravel\RevisionableTrait;
use Sofa\Revisionable\Revisionable;

class Dynamic extends Model implements Revisionable
{
    use RevisionableTrait;

    /**
     * @param $table
     */
    public function __construct($attributes = [])
    {
        parent::__construct($attributes);
    }

    /**
     * Dynamically set a model's table.
     *
     * @param  $table
     * @return void
     */
    public function setTable($table)
    {
        $this->table = $table;

        return $this;
    }
}

from : http://stackoverflow.com/questions/34700373/laravel-5-dynamically-create-eloquent-models

Use Schema::hasTable outside laravel

use Illuminate\Database\Capsule\Manager as Capsule;
use Illuminate\Database\Schema\Blueprint;

Capsule::schema()->hasTable

Git tips

還原所有更動

alias nah='git reset --hard;git clean -df;'

PHPUnit note

phpunit --filter [test_method]
Given(setup the world) -- When(What I do) -- Then(What I expected)

Multiple authentication guard drivers (including API) in Laravel 5.2

Let's get back to Laravel 5.2 features, shall we? 5.2 introduced a significant boost to the power of the entire authentication system, including making it much simpler to have multiple "guards" running at once.

Why should you care? #

The default authentication guard in Laravel prior to 5.2 (now named the web guard) is your traditional web-based application authentication layer: username and password post to a controller, which checks the credentials and redirects if they are invalid; if valid, the user information gets saved to the session. Not all of those pieces are absolutely necessary but that's the general mindset.

But what if you want to have an API running in the same app, and it uses JSON web tokens (or some other stateless, non-session authentication mechanism)? In the past you'd have to jump through a lot of hoops to have multiple authentication drivers running at the same time.

Laravel 5.2's default auth guards #

In 5.2, not only is it simple to have multiple auth drivers running, it actually already works that way out of the box.

If you check config/auth.php, you'll see two guards set out of the box: web, which is the classic Laravel authentication layer, and api, which is a stateless (no session memory) token-based driver.

Both, as you can see, connect to the same "provider".

Auth providers are also customizable. They're the definition of how the system should store and retrieve information about your users. Each is defined by an instance of Illuminate\Contracts\Auth\UserProvider.

    'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],

        'api' => [
            'driver' => 'token',
            'provider' => 'users',
        ],
    ],

If you look up higher in config/auth.php, you can see that the default Auth guard will be "web". That means any time you use Auth functions, middleware, or façades inside your application, they will default to the web guard unless you explicitly specify otherwise.

Introducing the token auth driver #

So, if web uses the classic session driver, what's this new token driver we're seeing powering the apiguard?

Jacob Bennett has written a fantastic post on that already: API Token Authentication in Laravel 5.2.

Check out his post to learn more about how it works, but here's the short of it:

• Add an api_token column to your users table. 60-character string, unique.
• Instead of using the auth middleware in your route definition, use the auth:api middleware.
• In your API routes, use Auth::guard('api')->user() to get your user instead of Auth::user().

As you can see, we need to store an api_token for each user, and every incoming request that's guarded by the token-driven api guard will require a query parameter named api_token with a valid API token set to authenticate that user. And since it's stateless, every request will need to have this API token set; one successful request won't affect the next request.

If you're not familiar with token-based authentication, the consuming application (e.g. an iOS application) will have gotten, and saved, the token for the authenticating user prior to this request, so it will be creating its API calls using that known token as a part of the URL. For example, an iOS app might want to get a list of its user's friends; when the user first authenticated the application with your web site/API the app received a token and stored it. Now, it will generate requests using URLs like this: http://yourapp.com/api/friends?api_token=STORED_TOKEN_HERE

Using non-default drivers #

As you can see in the token example above, there are two primary places we're going to be using drivers other than the default: in the auth guard middleware, and when we're using convenience features like Auth::check() and Auth::user() in our code.

You can choose which guard you're using to protect your routes by adding a colon and the guard name after auth in the middleware key (e.g. Route::get('whatever', ['middleware' => 'auth:api'])).

You can choose which guard you're calling manually in your code by making guard('guardname') the first call of a fluent chain every time you use the Auth façade (e.g. Auth::guard('api')->check()).

Creating your own guards and drivers #

Creating your own guard is simple, beause each guard is just a key (web, api) that points to a specific configuration of a driver (session, token) and a provider (users). They're configured, as mentioned above, in config/auth.php:

    'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],

        'api' => [
            'driver' => 'token',
            'provider' => 'users',
        ],
        'matts-fancy-api-guard' => [
            'driver' => 'token',
            'provider' => 'users',
        ],
    ],

But as you can tell, that doesn't really do much unless you're changing the driver or the provider.

Creating your own driver is not quite as simple as creating your own guard. The docs have a spot about Creating your own auth driver, and you're essentially going to be creating your own implementation of Illuminate\Contracts\Auth\Guard and then registering it as a driver in a service provider somewhere.

The docs also cover how to create your own user provider.

Concludinal #

That's it. Enjoy.

from : https://mattstauffer.co/blog/multiple-authentication-guard-drivers-including-api-in-laravel-5-2