暂无描述

ADmad b4c40a764f Bump up phpstan and psalm's version. 5 年之前
.github edd8275d54 Move codecov config file 5 年之前
config c295570ef5 Added float type annotation to TIME_START define 6 年之前
contrib 6314160643 Remove explicit standard from phpcs command. 7 年之前
src 1cad944075 Move warning about count() to top of docblock 5 年之前
templates 1c2e90c15e Fix indentation. 5 年之前
tests da31e03a7b Fix up PHPUnit usage. 5 年之前
.appveyor.yml 459e45bb0e Use env key matching interning array key. 5 年之前
.coveralls.yml b84db48447 Use coveralls instead of scrutinizer for code coverage reporting. 6 年之前
.editorconfig 72fc4cc8ec Remove unneeded line 6 年之前
.gitattributes e1facdf028 Add gitattributes php diff 5 年之前
.gitignore 2a28d9f743 Merge remote-tracking branch 'origin/3.next' into 4.x 6 年之前
.mailmap 8af28a5e99 Add o0h email to .mailmap 6 年之前
.stickler.yml 54fd0cf5dc Disable stickler's autofixer until it's kinks are sorted out. 6 年之前
.travis.yml f1b0b13faf Switch to codecov for code coverage reporting. 5 年之前
LICENSE 1d36e9fbc5 Update LICENSE 7 年之前
Makefile 73384c3d4f Fix another make compatibility issue. 5 年之前
README.md f1b0b13faf Switch to codecov for code coverage reporting. 5 年之前
SECURITY.md 4bb89e7c5c Add 4.0 to security policy 6 年之前
VERSION.txt d9f9c5739e Update version number to 4.1.4 5 年之前
composer.json b4c40a764f Bump up phpstan and psalm's version. 5 年之前
phpcs.xml.dist 9de1be1efc Use psalm specific annotations. 6 年之前
phpstan-baseline.neon b4c40a764f Bump up phpstan and psalm's version. 5 年之前
phpstan.neon bb95a89ee9 Normalize path 5 年之前
phpunit.xml.dist 459e45bb0e Use env key matching interning array key. 5 年之前
psalm-baseline.xml bbb167c26a Update psalm's baseline file. 5 年之前
psalm.xml d6430f4625 Bump up psalm's version. 5 年之前

README.md

CakePHP

Software License Build Status Coverage Status Code Consistency Total Downloads Latest Stable Version

CakePHP is a rapid development framework for PHP which uses commonly known design patterns like Associative Data Mapping, Front Controller, and MVC. Our primary goal is to provide a structured framework that enables PHP users at all levels to rapidly develop robust web applications, without any loss to flexibility.

Installing CakePHP via Composer

You can install CakePHP into your project using Composer. If you're starting a new project, we recommend using the app skeleton as a starting point. For existing applications you can run the following:

$ composer require cakephp/cakephp

Running Tests

Assuming you have PHPUnit installed system wide using one of the methods stated here, you can run the tests for CakePHP by doing the following:

  1. Copy phpunit.xml.dist to phpunit.xml.
  2. Add the relevant database credentials to your phpunit.xml if you want to run tests against a non-SQLite datasource.
  3. Run phpunit.

Some Handy Links

  • CakePHP - The rapid development PHP framework.
  • CookBook - The CakePHP user documentation; start learning here!
  • API - A reference to CakePHP's classes.
  • Awesome CakePHP - A list of featured resources around the framework.
  • Plugins - A repository of extensions to the framework.
  • The Bakery - Tips, tutorials and articles.
  • Community Center - A source for everything community related.
  • Training - Join a live session and get skilled with the framework.
  • CakeFest - Don't miss our annual CakePHP conference.
  • Cake Software Foundation - Promoting development related to CakePHP.

Get Support!

  • Slack - Join us on Slack.
  • #cakephp on irc.freenode.net - Come chat with us, we have cake.
  • Forum - Official CakePHP forum.
  • GitHub Issues - Got issues? Please tell us!
  • Roadmaps - Want to contribute? Get involved!

Contributing

Security

If you’ve found a security issue in CakePHP, please use the following procedure instead of the normal bug reporting system. Instead of using the bug tracker, mailing list or IRC please send an email to security [at] cakephp.org. Emails sent to this address go to the CakePHP core team on a private mailing list.

For each report, we try to first confirm the vulnerability. Once confirmed, the CakePHP team will take the following actions:

  • Acknowledge to the reporter that we’ve received the issue, and are working on a fix. We ask that the reporter keep the issue confidential until we announce it.
  • Get a fix/patch prepared.
  • Prepare a post describing the vulnerability, and the possible exploits.
  • Release new versions of all affected versions.
  • Prominently feature the problem in the release announcement.