暂无描述

Corey Taylor 85fcbd8a12 Update deprecation ignore paths for DateTimeTypeTest 4 年之前
.github aaccae1c32 Use phpstan level 1 to check basic tests sanity. 4 年之前
config c295570ef5 Added float type annotation to TIME_START define 6 年之前
contrib 6314160643 Remove explicit standard from phpcs command. 7 年之前
src 22bd32a076 Use default stackFrame for useImmutable/useMutable deprecation warning so points to bootstrap 4 年之前
templates abf0f75cf4 Add phpstan for tests. 4 年之前
tests 85fcbd8a12 Update deprecation ignore paths for DateTimeTypeTest 4 年之前
.editorconfig 2f30f947ba Preferred indentation style for .neon files is using tabs. 5 年之前
.gitattributes 3af4af9936 Update .gitattributes 5 年之前
.gitignore b229a964ec Dont use a dist for a non changing file 5 年之前
.mailmap 8af28a5e99 Add o0h email to .mailmap 6 年之前
.stickler.yml 54fd0cf5dc Disable stickler's autofixer until it's kinks are sorted out. 6 年之前
LICENSE 1d36e9fbc5 Update LICENSE 7 年之前
Makefile 73384c3d4f Fix another make compatibility issue. 5 年之前
README.md 108f4120a6 Add link to Discord server. 4 年之前
SECURITY.md e23d5fcf13 Mark 2.10.x as unsupported 4 年之前
VERSION.txt 1dd03223bf Update version number to 4.3.0-RC2 4 年之前
composer.json aaccae1c32 Use phpstan level 1 to check basic tests sanity. 4 年之前
phpcs.xml 936a6e0b52 Show phpcs sniff with each error 5 年之前
phpstan-baseline.neon ff48a69617 Merge pull request #15958 from cakephp/4.next-fixes 4 年之前
phpstan.neon 2f30f947ba Preferred indentation style for .neon files is using tabs. 5 年之前
phpunit.xml.dist 9b6725af2b Fix BC breaking change of PHPUnit 9.5.10 4 年之前
psalm-baseline.xml 40c438d6c8 Mark TestCase::loadFixtures() deprecated 4 年之前
psalm.xml 8ea74a848c Start documenting the assoc arrays as per their string key. 4 年之前

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

For details on the (minimum/maximum) PHP version see version map.

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.
  • Discord - Join us on Discord.
  • #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.