About integrating Qiniu Cloud Storage in Laravel 5 to realize cloud storage function

About integrating Qiniu Cloud Storage in Laravel 5 to realize cloud storage function

Using Qiniu official SDK, non-storage version
The method is very simple, only the Composer installation method is introduced, as follows:

Install Composer

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

Run the Composer command to install the latest stable version of the SDK:

php composer.phar require qiniu/php-sdk

Require the autoloader generated by Composer: Regarding the third step, personally I think it will be loaded automatically after installation using Composer. I don’t know if there is any misunderstanding. I still don’t know much about how it operates. If there are any errors, please point them out
If you need more detailed instructions for using Composer, you can visit Composer official website, or the corresponding Chinese website.
After the above steps are completed, the following is a very important link

require 'vendor/autoload.php';

There are many novices like me who may find that they can use it directly according to the official tutorial. There may be Auth conflicts~~~
There are ways to solve it here, don’t be discouraged, such as:

use QiniuAuth as QiAuth;

Use an alias to rename it, no need to modify the source code

Below, Our steps are basically the same as the official tutorial:
First, we need to authenticate:

// The space to be uploaded

$bucket = 'life';

// The public key and private key used for signing

$ accessKey = 'Access_Key';

$secretKey = 'Secret_Key';

Initialize the signature object

$auth = new QiAuth($accessKey, $secretKey);

// Generate upload Token

$upload_token = $auth ->uploadToken($bucket);

At this point, we have completed the basic background operations. Now we will process the form

<form method="post" action="http://up.qiniu.com" enctype="multipart/form-data">
<input name="token" type="hidden" value="{{upload_token}}">
<input name="file" type="file" />
<input type="submit" value="上传"/>
</form>

Here, I made a very low-level mistake. When processing the token, the label I wrote it wrong, which led to a long time of troubleshooting~~~