Updated package to laravel 5.1 package conventions. Now we publish mi…

…grations instead of keeping them in the package directory structure.

Ready for Laravel 5.1 :D

README.md

@@ -62,10 +62,13 @@ Run a **composer update**.
    );
 ```
 
-### Step 3: Migrate tables
+### Step 3: Publish migrations and config
+
 ```
-$ php artisan migrate --package="triggerdesign/hermes"
+    php artisan vendor:publish
+    php artisan migrate
 ```
+
 Now you have the 4 tables that we need for user conversations.
 
 ### Step 4: Use the user trait 

src/Triggerdesign/Hermes/HermesServiceProvider.php

@@ -24,15 +24,18 @@ public function boot()
         });
 
         $this->publishes([
-            __DIR__.'/../config/config.php' => config_path('hermes.php'),
+            __DIR__.'/../../config/config.php' => config_path('hermes.php'),
+            __DIR__.'/../../migrations/' => database_path('/migrations'),
+
         ]);
 
 
         app()->bind('hermes::command.migration', function(){
             return new \MigrationCommand();
         });
 
-        $this->commands(['hermes::command.migration']);
+        //Use the published migration instead of a command (the documented Laravel 5.1 way)
+        //$this->commands(['hermes::command.migration']);
 
 	}
 

src/commands/MigrationCommand.php

@@ -15,6 +15,10 @@ class MigrationCommand extends Command{
      */
     protected $description = 'Migrate the necessary package migration files for hermes (messages, conversations, conversation_user, message_states).';
 
+    public function __construct(){
+        $this->app = app();
+    }
+
     /**
      * Run the package migrations
      */