暂无描述

Mark Story de02e62b08 Merge pull request #14340 from cakephp/3.x-cache-probability 6 年之前
.github eec7c5aa52 Backport from 4.x 6 年之前
config 44a78128e7 Fix CS for easier 3.x/4.x comparison/merge. 6 年之前
contrib 79771590f1 Add linting as suggested by @jrbasso 11 年之前
src 5a222e601e Fix division by 0 when configuring Cache with probability of 0 6 年之前
tests 5a222e601e Fix division by 0 when configuring Cache with probability of 0 6 年之前
.appveyor.yml 9ac915ff84 Upgrade pdo_sqlsrv 6 年之前
.editorconfig 5749a812b5 Add identation style for Makefile to .editorconfig 6 年之前
.gitattributes 90d412c43e Merge pull request #14014 from othercorey/remove-varci 6 年之前
.gitignore ff4127a410 Fixup in_array() and pure string usage, string[] docs and merging. 6 年之前
.mailmap 266f1c9f27 Update .mailmap 7 年之前
.scrutinizer.yml 20a4e57a42 Add .scrutinizer.yml 10 年之前
.stickler.yml 1b8a8c8eb4 Enable automatic PHPCS fixing from stickler 8 年之前
.travis.yml eaa84609f3 Reduce the number of php configs in travis 6 年之前
LICENSE 1d36e9fbc5 Update LICENSE 7 年之前
Makefile f0a9faadf4 Set branch for app in 3.x 6 年之前
README.md 01f4a69915 Updated links from book.cakephp.org/3.0/ to book.cakephp.org/3/ 6 年之前
SECURITY.md 62911c86ee Adding SECURITY.md 6 年之前
VERSION.txt a5b75c3a9d Update version number to 3.8.10 6 年之前
composer.json 147fafc0d1 Fix docblock/phpstan error. Improve phpstan run. 6 年之前
phpcs.xml.dist 3f0bdd6ff3 Exclude TODO sniff for 3.next development 7 年之前
phpstan.neon d586c759c3 Allow using DateTimeImmutable instance. 7 年之前
phpunit.xml.dist b2f53ed625 Remove outdated configs 6 年之前

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.