├── .gitignore ├── .scrutinizer.yml ├── .travis.yml ├── CHANGELOG.md ├── CONDUCT.md ├── CONTRIBUTING.md ├── ISSUE_TEMPLATE.md ├── LICENSE ├── PULL_REQUEST_TEMPLATE.md ├── README.md ├── composer.json ├── phpunit.php ├── phpunit.xml ├── src ├── BackblazeB2Exception.php └── BackblazeB2ServiceProvider.php └── tests └── BackblazeB2ServiceProviderTests.php /.gitignore: -------------------------------------------------------------------------------- 1 | build 2 | composer.lock 3 | docs 4 | vendor 5 | coverage 6 | coverage.xml 7 | .idea -------------------------------------------------------------------------------- /.scrutinizer.yml: -------------------------------------------------------------------------------- 1 | filter: 2 | paths: [src/*] 3 | checks: 4 | php: 5 | code_rating: true 6 | remove_extra_empty_lines: true 7 | remove_php_closing_tag: true 8 | remove_trailing_whitespace: true 9 | fix_use_statements: 10 | remove_unused: true 11 | preserve_multiple: false 12 | preserve_blanklines: true 13 | order_alphabetically: true 14 | fix_php_opening_tag: true 15 | fix_linefeed: true 16 | fix_line_ending: true 17 | fix_identation_4spaces: true 18 | fix_doc_comments: true 19 | tools: 20 | php_code_coverage: true 21 | php_code_sniffer: 22 | config: 23 | standard: PSR2 24 | filter: 25 | paths: ['src'] 26 | php_loc: 27 | enabled: true 28 | php_cpd: 29 | enabled: true 30 | -------------------------------------------------------------------------------- /.travis.yml: -------------------------------------------------------------------------------- 1 | language: php 2 | 3 | php: 4 | - 7.1 5 | - hhvm 6 | 7 | install: 8 | - travis_retry composer install --no-interaction --prefer-source 9 | 10 | script: 11 | - vendor/bin/phpunit 12 | 13 | after_script: 14 | - wget https://scrutinizer-ci.com/ocular.phar 15 | - bash -c 'if [ "$TRAVIS_PHP_VERSION" != "hhvm" ]; then php ocular.phar code-coverage:upload --format=php-clover coverage.xml; fi;' 16 | -------------------------------------------------------------------------------- /CHANGELOG.md: -------------------------------------------------------------------------------- 1 | # Changelog 2 | 3 | All Notable changes to `laravel-backblaze-b2` will be documented in this file. 4 | 5 | Updates should follow the [Keep a CHANGELOG](http://keepachangelog.com/) principles. 6 | 7 | ## NEXT - YYYY-MM-DD 8 | 9 | ### Added 10 | - Nothing 11 | 12 | ### Deprecated 13 | - Nothing 14 | 15 | ### Fixed 16 | - Nothing 17 | 18 | ### Removed 19 | - Nothing 20 | 21 | ### Security 22 | - Nothing 23 | -------------------------------------------------------------------------------- /CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Contributor Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | In the interest of fostering an open and welcoming environment, we as 6 | contributors and maintainers pledge to making participation in our project and 7 | our community a harassment-free experience for everyone, regardless of age, body 8 | size, disability, ethnicity, gender identity and expression, level of experience, 9 | nationality, personal appearance, race, religion, or sexual identity and 10 | orientation. 11 | 12 | ## Our Standards 13 | 14 | Examples of behavior that contributes to creating a positive environment 15 | include: 16 | 17 | * Using welcoming and inclusive language 18 | * Being respectful of differing viewpoints and experiences 19 | * Gracefully accepting constructive criticism 20 | * Focusing on what is best for the community 21 | * Showing empathy towards other community members 22 | 23 | Examples of unacceptable behavior by participants include: 24 | 25 | * The use of sexualized language or imagery and unwelcome sexual attention or 26 | advances 27 | * Trolling, insulting/derogatory comments, and personal or political attacks 28 | * Public or private harassment 29 | * Publishing others' private information, such as a physical or electronic 30 | address, without explicit permission 31 | * Other conduct which could reasonably be considered inappropriate in a 32 | professional setting 33 | 34 | ## Our Responsibilities 35 | 36 | Project maintainers are responsible for clarifying the standards of acceptable 37 | behavior and are expected to take appropriate and fair corrective action in 38 | response to any instances of unacceptable behavior. 39 | 40 | Project maintainers have the right and responsibility to remove, edit, or 41 | reject comments, commits, code, wiki edits, issues, and other contributions 42 | that are not aligned to this Code of Conduct, or to ban temporarily or 43 | permanently any contributor for other behaviors that they deem inappropriate, 44 | threatening, offensive, or harmful. 45 | 46 | ## Scope 47 | 48 | This Code of Conduct applies both within project spaces and in public spaces 49 | when an individual is representing the project or its community. Examples of 50 | representing a project or community include using an official project e-mail 51 | address, posting via an official social media account, or acting as an appointed 52 | representative at an online or offline event. Representation of a project may be 53 | further defined and clarified by project maintainers. 54 | 55 | ## Enforcement 56 | 57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be 58 | reported by contacting the project team at `contact@yeello.com`. All 59 | complaints will be reviewed and investigated and will result in a response that 60 | is deemed necessary and appropriate to the circumstances. The project team is 61 | obligated to maintain confidentiality with regard to the reporter of an incident. 62 | Further details of specific enforcement policies may be posted separately. 63 | 64 | Project maintainers who do not follow or enforce the Code of Conduct in good 65 | faith may face temporary or permanent repercussions as determined by other 66 | members of the project's leadership. 67 | 68 | ## Attribution 69 | 70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, 71 | available at [http://contributor-covenant.org/version/1/4][version] 72 | 73 | [homepage]: http://contributor-covenant.org 74 | [version]: http://contributor-covenant.org/version/1/4/ 75 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing 2 | 3 | Contributions are **welcome** and will be fully **credited**. 4 | 5 | We accept contributions via Pull Requests on [Github](https://github.com/gliterd/laravel-backblaze-b2). 6 | 7 | 8 | ## Pull Requests 9 | 10 | - **[PSR-2 Coding Standard](https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md)** - The easiest way to apply the conventions is to install [PHP Code Sniffer](http://pear.php.net/package/PHP_CodeSniffer). 11 | 12 | - **Add tests!** - Your patch won't be accepted if it doesn't have tests. 13 | 14 | - **Document any change in behaviour** - Make sure the `README.md` and any other relevant documentation are kept up-to-date. 15 | 16 | - **Consider our release cycle** - We try to follow [SemVer v2.0.0](http://semver.org/). Randomly breaking public APIs is not an option. 17 | 18 | - **Create feature branches** - Don't ask us to pull from your master branch. 19 | 20 | - **One pull request per feature** - If you want to do more than one thing, send multiple pull requests. 21 | 22 | - **Send coherent history** - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please [squash them](http://www.git-scm.com/book/en/v2/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages) before submitting. 23 | 24 | 25 | ## Running Tests 26 | 27 | ``` bash 28 | $ composer test 29 | ``` 30 | 31 | 32 | **Happy coding**! 33 | -------------------------------------------------------------------------------- /ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Detailed description 4 | 5 | Provide a detailed description of the change or addition you are proposing. 6 | 7 | Make it clear if the issue is a bug, an enhancement or just a question. 8 | 9 | ## Context 10 | 11 | Why is this change important to you? How would you use it? 12 | 13 | How can it benefit other users? 14 | 15 | ## Possible implementation 16 | 17 | Not obligatory, but suggest an idea for implementing addition or change. 18 | 19 | ## Your environment 20 | 21 | Include as many relevant details about the environment you experienced the bug in and how to reproduce it. 22 | 23 | * Version used (e.g. PHP 5.6, HHVM 3): 24 | * Operating system and version (e.g. Ubuntu 16.04, Windows 7): 25 | * Link to your project: 26 | * ... 27 | * ... 28 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2017 Gliterd Software 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Description 4 | 5 | Describe your changes in detail. 6 | 7 | ## Motivation and context 8 | 9 | Why is this change required? What problem does it solve? 10 | 11 | If it fixes an open issue, please link to the issue here (if you write `fixes #num` 12 | or `closes #num`, the issue will be automatically closed when the pull is accepted.) 13 | 14 | ## How has this been tested? 15 | 16 | Please describe in detail how you tested your changes. 17 | 18 | Include details of your testing environment, and the tests you ran to 19 | see how your change affects other areas of the code, etc. 20 | 21 | ## Screenshots (if appropriate) 22 | 23 | ## Types of changes 24 | 25 | What types of changes does your code introduce? Put an `x` in all the boxes that apply: 26 | - [ ] Bug fix (non-breaking change which fixes an issue) 27 | - [ ] New feature (non-breaking change which adds functionality) 28 | - [ ] Breaking change (fix or feature that would cause existing functionality to change) 29 | 30 | ## Checklist: 31 | 32 | Go over all the following points, and put an `x` in all the boxes that apply. 33 | 34 | Please, please, please, don't send your pull request until all of the boxes are ticked. 35 | 36 | - [ ] I have read the **[CONTRIBUTING](CONTRIBUTING.md)** document. 37 | - [ ] My pull request addresses exactly one patch/feature. 38 | - [ ] I have created a branch for this patch/feature. 39 | - [ ] Each individual commit in the pull request is meaningful. 40 | - [ ] I have added tests to cover my changes. 41 | - [ ] All new and existing tests passed. 42 | - [ ] If my change requires a change to the documentation, I have updated it accordingly. 43 | - [ ] My code follows the code style of this project. 44 | 45 | If you're unsure about any of these, don't hesitate to ask. We're here to help! 46 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # laravel-backblaze-b2 2 | 3 | [![Author](http://img.shields.io/badge/author-@mhetreramesh-blue.svg?style=flat-square)](https://twitter.com/mhetreramesh) 4 | [![Latest Version on Packagist](https://img.shields.io/packagist/v/gliterd/laravel-backblaze-b2.svg?style=flat-square)](https://packagist.org/packages/gliterd/laravel-backblaze-b2) 5 | [![Software License][ico-license]](LICENSE.md) 6 | [![Build Status](https://img.shields.io/travis/gliterd/laravel-backblaze-b2/master.svg?style=flat-square)](https://travis-ci.org/gliterd/laravel-backblaze-b2) 7 | [![Coverage Status][ico-scrutinizer]][link-scrutinizer] 8 | [![Quality Score][ico-code-quality]][link-code-quality] 9 | [![Total Downloads](https://img.shields.io/packagist/dt/gliterd/laravel-backblaze-b2.svg?style=flat-square)](https://packagist.org/packages/gliterd/laravel-backblaze-b2) 10 | 11 | Visit (https://secure.backblaze.com/b2_buckets.htm) and get your account id, application key. 12 | 13 | The Laravel Backblaze B2 Storage Service Provider give provision for for laravel storage to use blackblaze as their storage system. It uses the [Backblaze B2 SDK](https://github.com/gliterd/backblaze-b2) & [Flysystem Adapter](https://github.com/gliterd/flysystem-backblaze) to communicate with the Backblaze b2 API. 14 | 15 | ## Install 16 | 17 | Via Composer 18 | 19 | ``` bash 20 | composer require gliterd/laravel-backblaze-b2 21 | ``` 22 | In your app.php config file add to the list of service providers: 23 | 24 | ``` php 25 | \Gliterd\BackblazeB2\BackblazeB2ServiceProvider::class, 26 | ``` 27 | Add the following to your filesystems.php config file in the disks section: 28 | ``` php 29 | 'b2' => [ 30 | 'driver' => 'b2', 31 | 'accountId' => '', 32 | 'applicationKey' => '', 33 | 'bucketName' => '', 34 | 'bucketId' => '', //optional 35 | ], 36 | ``` 37 | ## Using ApplicationKey instead of MasterKey 38 | If you specify only the bucket name, your application key must be the master key. 39 | However, if you specify both bucket name and bucket id, you do not need the master key and can use a single-bucket key. 40 | Fetch your bucket id using the [b2 command line tool](https://www.backblaze.com/b2/docs/quick_command_line.html) `b2 get-bucket ` 41 | 42 | ## Usage 43 | 44 | Just use it as you normally would use the Storage facade. 45 | 46 | ``` php 47 | \Storage::disk('b2')->put('filename.txt', 'My important content'); 48 | ``` 49 | and 50 | ``` php 51 | \Storage::disk('b2')->get('filename.txt') 52 | ``` 53 | 54 | ## Change log 55 | 56 | Please see [CHANGELOG](CHANGELOG.md) for more information what has changed recently. 57 | 58 | ## Testing 59 | 60 | ``` bash 61 | $ composer test 62 | ``` 63 | 64 | ## Contributing 65 | 66 | Please see [CONTRIBUTING](CONTRIBUTING.md) and [CONDUCT](CONDUCT.md) for details. 67 | 68 | ## Security 69 | 70 | If you discover any security related issues, please email mhetreramesh@gmail.com instead of using the issue tracker. 71 | 72 | ## Credits 73 | 74 | - [Ramesh Mhetre][link-author] 75 | - [All Contributors][link-contributors] 76 | 77 | ## License 78 | 79 | The MIT License (MIT). Please see [License File](LICENSE.md) for more information. 80 | 81 | [ico-version]: https://img.shields.io/packagist/v/gliterd/laravel-backblaze-b2.svg?style=flat-square 82 | [ico-license]: https://img.shields.io/badge/license-MIT-brightgreen.svg?style=flat-square 83 | [ico-travis]: https://img.shields.io/travis/gliterd/laravel-backblaze-b2/master.svg?style=flat-square 84 | [ico-scrutinizer]: https://img.shields.io/scrutinizer/coverage/g/gliterd/laravel-backblaze-b2.svg?style=flat-square 85 | [ico-code-quality]: https://img.shields.io/scrutinizer/g/gliterd/laravel-backblaze-b2.svg?style=flat-square 86 | [ico-downloads]: https://img.shields.io/packagist/dt/gliterd/laravel-backblaze-b2.svg?style=flat-square 87 | 88 | [link-packagist]: https://packagist.org/packages/gliterd/laravel-backblaze-b2 89 | [link-travis]: https://travis-ci.org/gliterd/laravel-backblaze-b2 90 | [link-scrutinizer]: https://scrutinizer-ci.com/g/gliterd/laravel-backblaze-b2/code-structure 91 | [link-code-quality]: https://scrutinizer-ci.com/g/gliterd/laravel-backblaze-b2 92 | [link-downloads]: https://packagist.org/packages/gliterd/laravel-backblaze-b2 93 | [link-author]: https://github.com/mhetreramesh 94 | [link-contributors]: ../../contributors 95 | -------------------------------------------------------------------------------- /composer.json: -------------------------------------------------------------------------------- 1 | { 2 | "name": "gliterd/laravel-backblaze-b2", 3 | "type": "library", 4 | "description": "Backblaze B2 Cloud Storage for Laravel 5", 5 | "keywords": ["flysystem", "filesystem", "api", "backblaze", "laravel", "storage", "disks"], 6 | "homepage": "https://github.com/mhetreramesh/flysystem-backblaze", 7 | "license": "MIT", 8 | "authors": [ 9 | { 10 | "name": "Ramesh Mhetre", 11 | "email": "mhetreramesh@gmail.com", 12 | "homepage": "https://about.me/rameshmhetre", 13 | "role": "Developer" 14 | } 15 | ], 16 | "require": { 17 | "php": "^7.1.8", 18 | "mhetreramesh/flysystem-backblaze": ">=1.6.0" 19 | }, 20 | "require-dev": { 21 | "phpunit/phpunit" : "~4.0||~5.0", 22 | "scrutinizer/ocular": "~1.1", 23 | "squizlabs/php_codesniffer": "~2.3" 24 | }, 25 | "autoload": { 26 | "psr-4": { 27 | "Gliterd\\BackblazeB2\\": "src" 28 | } 29 | }, 30 | "autoload-dev": { 31 | "psr-4": { 32 | "Gliterd\\BackblazeB2\\Tests\\": "tests" 33 | } 34 | }, 35 | "scripts": { 36 | "test": "phpunit", 37 | "format": "phpcbf --standard=psr2 src/" 38 | }, 39 | "config": { 40 | "sort-packages": true 41 | }, 42 | "extra": { 43 | "laravel": { 44 | "providers": [ 45 | "\\Gliterd\\BackblazeB2\\BackblazeB2ServiceProvider" 46 | ] 47 | } 48 | } 49 | } 50 | -------------------------------------------------------------------------------- /phpunit.php: -------------------------------------------------------------------------------- 1 | 2 | 14 | 15 | 16 | ./tests/ 17 | 18 | 19 | 20 | 21 | ./src/ 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | -------------------------------------------------------------------------------- /src/BackblazeB2Exception.php: -------------------------------------------------------------------------------- 1 | assertEquals('test', 'test'); 10 | } 11 | } 12 | --------------------------------------------------------------------------------