|
||
---|---|---|
.github | ||
assets | ||
commands | ||
config | ||
controllers | ||
mail/layouts | ||
models | ||
runtime | ||
tests | ||
utils | ||
vagrant | ||
views | ||
web | ||
widgets | ||
.bowerrc | ||
.gitattributes | ||
.gitignore | ||
codeception.yml | ||
composer.json | ||
docker-compose.yml | ||
LICENSE.md | ||
qodana.yaml | ||
README.md | ||
requirements.php | ||
Vagrantfile | ||
yii | ||
yii.bat |
基于Yii 2框架的网盘系统
这是一个基于Yii 2 PHP框架设计的小型网盘系统,作为我的毕业设计作业,它具备基本的网盘功能。
这个项目基于Yii 2 基础项目模板,使用了模板中较少一部分的内容作为项目的一部分。
项目结构
assets/ contains assets definition
commands/ contains console commands (controllers)
config/ contains application configurations
controllers/ contains Web controller classes
mail/ contains view files for e-mails
models/ contains model classes
runtime/ contains files generated during runtime
tests/ contains various tests for the basic application
vendor/ contains dependent 3rd-party packages
views/ contains view files for the Web application
web/ contains the entry script and Web resources
目前已实现的功能
用户登录、注册
目录显示
文件操作(下载,删除,重命名)
文件夹操作(打包下载,删除,重命名)
文件/文件夹上传(支持拖拽上传文件)
批量操作,打包,下载
计划实现的功能
批量删除,复制,剪切,粘贴,解压
登录验证码
文件校验信息查看
文件预览
文件/文件夹分享
分享管理
交互性提升(右键菜单)
个人资料管理
访问控制
系统设置
设计主页,删除无用页面
EXTRA: 客户端开发
运行所需环境
PHP >= 8.1
MySQL/MariaDB
安装步骤
通过压缩档案进行安装
在本项目的release下载最新版本的归档文件,解压到web根目录下.
执行composer install,安装必要的依赖项。
在config/web.php
文件中设置一些随机的密钥:
'request' => [
// !!! insert a secret key in the following (if it is empty) - this is required by cookie validation
'cookieValidationKey' => '<secret random string goes here>',
],
现在你可以通过以下链接访问你的站点:
http://localhost/basic/web/
配置
数据库
像这样修改config/db.php文件:
return [
'class' => 'yii\db\Connection',
'dsn' => 'mysql:host=localhost;dbname=yii2basic',
'username' => 'root',
'password' => '1234',
'charset' => 'utf8',
];
提示:
- 我们不会帮你创建好数据库,请在使用项目前自行创建。
- 检查
config/
目录下的其他配置文件以客制化你的安装。
TESTING
Tests are located in tests
directory. They are developed with Codeception PHP Testing Framework.
By default, there are 3 test suites:
unit
functional
acceptance
Tests can be executed by running
vendor/bin/codecept run
The command above will execute unit and functional tests. Unit tests are testing the system components, while functional tests are for testing user interaction. Acceptance tests are disabled by default as they require additional setup since they perform testing in real browser.
Running acceptance tests
To execute acceptance tests do the following:
-
Rename
tests/acceptance.suite.yml.example
totests/acceptance.suite.yml
to enable suite configuration -
Replace
codeception/base
package incomposer.json
withcodeception/codeception
to install full-featured version of Codeception -
Update dependencies with Composer
composer update
-
Download Selenium Server and launch it:
java -jar ~/selenium-server-standalone-x.xx.x.jar
In case of using Selenium Server 3.0 with Firefox browser since v48 or Google Chrome since v53 you must download GeckoDriver or ChromeDriver and launch Selenium with it:
# for Firefox java -jar -Dwebdriver.gecko.driver=~/geckodriver ~/selenium-server-standalone-3.xx.x.jar # for Google Chrome java -jar -Dwebdriver.chrome.driver=~/chromedriver ~/selenium-server-standalone-3.xx.x.jar
As an alternative way you can use already configured Docker container with older versions of Selenium and Firefox:
docker run --net=host selenium/standalone-firefox:2.53.0
-
(Optional) Create
yii2basic_test
database and update it by applying migrations if you have them.tests/bin/yii migrate
The database configuration can be found at
config/test_db.php
. -
Start web server:
tests/bin/yii serve
-
Now you can run all available tests
# run all available tests vendor/bin/codecept run # run acceptance tests vendor/bin/codecept run acceptance # run only unit and functional tests vendor/bin/codecept run unit,functional
Code coverage support
By default, code coverage is disabled in codeception.yml
configuration file, you should uncomment needed rows to be able
to collect code coverage. You can run your tests and collect coverage with the following command:
#collect coverage for all tests
vendor/bin/codecept run --coverage --coverage-html --coverage-xml
#collect coverage only for unit tests
vendor/bin/codecept run unit --coverage --coverage-html --coverage-xml
#collect coverage for unit and functional tests
vendor/bin/codecept run functional,unit --coverage --coverage-html --coverage-xml
You can see code coverage output under the tests/_output
directory.