説明なし

othercorey 97fc4c857a Fixed typos 5 年 前
.github 1db878fee9 Use memcache docker image instead of apt package. 5 年 前
config c295570ef5 Added float type annotation to TIME_START define 6 年 前
contrib 6314160643 Remove explicit standard from phpcs command. 7 年 前
src 33bf6d2e30 Fix Hash::mergeDiff() not handling scalar values. 5 年 前
templates 97fc4c857a Fixed typos 5 年 前
tests 33bf6d2e30 Fix Hash::mergeDiff() not handling scalar values. 5 年 前
.coveralls.yml b84db48447 Use coveralls instead of scrutinizer for code coverage reporting. 6 年 前
.editorconfig 2f30f947ba Preferred indentation style for .neon files is using tabs. 5 年 前
.gitattributes d30cfd623b Adjust gitattributes for phpcs.xml 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 60a86747bb Clarify version map 5 年 前
SECURITY.md 4bb89e7c5c Add 4.0 to security policy 6 年 前
VERSION.txt d8c526bb3e Update version number to 4.1.6 5 年 前
composer.json 13762dc9c8 Upgrade psalm to 3.18 5 年 前
phpcs.xml b229a964ec Dont use a dist for a non changing file 5 年 前
phpstan-baseline.neon b4c40a764f Bump up phpstan and psalm's version. 5 年 前
phpstan.neon 2f30f947ba Preferred indentation style for .neon files is using tabs. 5 年 前
phpunit.xml.dist f6606b7ade MySQL name correctly 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

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.
  • #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.