larkinwhitaker / laravel-db-backup Goto Github PK

Im getting following error, on Laravel 5.2

Problem 1
- Conclusion: don't install laravel/framework v5.2.3
- Conclusion: don't install laravel/framework v5.2.2
- Conclusion: don't install laravel/framework v5.2.1
- Conclusion: don't install laravel/framework v5.2.0
- Conclusion: don't install laravel/framework v5.2.0-beta1
- witty/laravel-db-backup dev-master requires illuminate/support 5.0.* | 5.1.* -> satisfiable by laravel/framework[v5.1.24, 5.0.x-dev, 5.1.x-dev], illuminate/support[5.0.x-dev, 5.1.x-dev, v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.6, v5.1.8].
- witty/laravel-db-backup dev-master requires illuminate/support 5.0.* | 5.1.* -> satisfiable by laravel/framework[v5.1.24, 5.0.x-dev, 5.1.x-dev], illuminate/support[5.0.x-dev, 5.1.x-dev, v5.0.0, v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.0.4, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.6, v5.1.8].
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support 5.0.x-dev
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support 5.1.x-dev
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.0.0
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.0.22
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.0.25
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.0.26
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.0.28
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.0.33
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.0.4
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.1.1
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.1.13
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.1.16
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.1.2
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.1.20
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.1.22
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.1.25
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.1.6
- don't install laravel/framework 5.2.x-dev|don't install illuminate/support v5.1.8
- Can only install one of: laravel/framework[5.2.x-dev, 5.0.x-dev].
- Can only install one of: laravel/framework[5.2.x-dev, 5.1.x-dev].
- Can only install one of: laravel/framework[5.2.x-dev, v5.1.24].
- Installation request for laravel/framework 5.2.* -> satisfiable by laravel/framework[5.2.x-dev, v5.2.0, v5.2.0-beta1, v5.2.1, v5.2.2, v5.2.3].
- Installation request for witty/laravel-db-backup dev-master -> satisfiable by witty/laravel-db-backup[dev-master].

When running:
php artisan db:backup --upload-s3 my-bucket

I get the following error message " [BadMethodCallException]
Unknown method: get.
"

Commands/BackupCommand#123
It works fine if I change
$s3 = AWS::get('s3');
to
$s3 = AWS::createClient('s3');

Any plans to support restoring databases from S3?

Hi Guys,

This use line is throwing an error as my AWS package doesn't have the Laravel namespace:
use Aws\Laravel\AwsFacade as AWS;

I'm using the aws SDK from the laravel docs and have lots of other areas of my site that upload to s3 so fairly sure that's set up correctly.

Anyone no how to fix this without editing the package files?

Please add an option to purge the database before restoring a backup: drop all tables, views, stored procedures etc. but NOT user permissions for the database (i.e. NOT drop database and recreate!).

Rationale: the "backup, migration FAIL, restore" work cycle. Laravel migrations, with their DREADED AND CURSED inability to recover from failures properly, eventually force every laravel programmer to employ some kind of database backup/restore solution so that the database can be backed up before every attempt at artisan migrate and restored when the migration fails due to a stupid coding mistake in the newest migration file. The whole point is to be able to restore the database to the EXACT same state as before the attempted migration. Currently if the migration creates some tables then these tables will still be there after restoring the backup, and a subsequent attempt at migration will fail because those tables already exist. The whole point is to avoid this DREADED AND CURSED scenario.

That package works fine in the terminal with this command php artisan db:back --database=mysql but when i try to execute via the controller code, it doesn't work and this is my code snipped-

 Artisan::call('db:backup',['--database'=>'mysql']);//this is command
    
 return Redirect::back()->with('success','Database backup was successful, 
.SQL file was saved in dump folder.');

I also try with this code but doesn't work

Artisan::call('db:backup',['--database'=>'mysql']);
Artisan::call('db:backup');
Please, anyone, help me out exactly where is the problem?