Skip to content
CakePHP: The Rapid Development Framework for PHP - Official Repository
PHP CSS Makefile Hack Shell HTML
Branch: master
Clone or download

Latest commit

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Cache PHP extensions Mar 2, 2020
config Added float type annotation to TIME_START define Apr 13, 2020
contrib Remove explicit standard from phpcs command. Feb 4, 2019
src Add description for `@method` annotations. Jun 2, 2020
templates Fix CS. May 20, 2020
tests Fix type error, abs() doesn't accept string. May 31, 2020
.appveyor.yml Aligned appveyor config with rest of cakephp Dec 21, 2019
.coveralls.yml Use coveralls instead of scrutinizer for code coverage reporting. Aug 6, 2019
.editorconfig Remove unneeded line Mar 29, 2020
.gitattributes Merge remote-tracking branch 'origin/3.next' into 4.x Dec 14, 2019
.gitignore Merge remote-tracking branch 'origin/master' into 3.next Nov 19, 2019
.mailmap Add o0h email to .mailmap Jan 7, 2020
.stickler.yml Disable stickler's autofixer until it's kinks are sorted out. Dec 9, 2019
.travis.yml Run testsuite on PHP 8 May 29, 2020
LICENSE Update LICENSE Jan 2, 2019
Makefile Run post install command. Dec 30, 2019
README.md Updated travis-ci.com link Mar 28, 2020
SECURITY.md Add 4.0 to security policy Mar 1, 2020
VERSION.txt Update version number to 4.0.8 May 24, 2020
composer.json Fix errors reported by psalm Apr 17, 2020
phpcs.xml.dist Undo changes to phpcs.xml.dist. Oct 1, 2019
phpstan-baseline.neon Update phpstan's baseline file May 10, 2020
phpstan.neon Update phpstan config Feb 20, 2020
phpunit.xml.dist Ignore class loader in coverage. Jan 17, 2020
psalm-baseline.xml Enable psalm's type coercion check. May 4, 2020
psalm.xml Upate psalm's annotations/config. May 11, 2020

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.
You can’t perform that action at this time.