No Description

Corey Taylor 58735641ec Merge branch 'master' into 4.next 6 years ago
.github 9de88c72fe Run CI worflow for push to master and 4.next 6 years ago
config 035fee0926 Avoid using CORE_PATH constant to read VERSION.txt file. 6 years ago
contrib 6314160643 Remove explicit standard from phpcs command. 7 years ago
src 58735641ec Merge branch 'master' into 4.next 6 years ago
templates 749597b4c7 Fix mistakes 6 years ago
tests 58735641ec Merge branch 'master' into 4.next 6 years ago
.appveyor.yml 3eb813d4eb Aligned appveyor config with rest of cakephp 6 years ago
.coveralls.yml b84db48447 Use coveralls instead of scrutinizer for code coverage reporting. 6 years ago
.editorconfig 7a4c880bd6 Forward port 3.next into 4.x. 6 years ago
.gitattributes dd4d158771 Merge remote-tracking branch 'origin/3.next' into 4.x 6 years ago
.gitignore 2a28d9f743 Merge remote-tracking branch 'origin/3.next' into 4.x 6 years ago
.mailmap 266f1c9f27 Update .mailmap 7 years ago
.stickler.yml 54fd0cf5dc Disable stickler's autofixer until it's kinks are sorted out. 6 years ago
.travis.yml 3f39a2dfad Update Github CI workflow and travis config. 6 years ago
LICENSE 1d36e9fbc5 Update LICENSE 7 years ago
Makefile adbe61881f Merge branch '3.next' 6 years ago
README.md e7a7da7b54 Updated all book.cakephp.org links to /4/ 6 years ago
SECURITY.md 62911c86ee Adding SECURITY.md 6 years ago
VERSION.txt 1c54e201f8 Bump version for 4.1-dev 6 years ago
composer.json a65a707a98 Just use phpunit ~8.5.0 6 years ago
phpcs.xml.dist 9de1be1efc Use psalm specific annotations. 6 years ago
phpstan-baseline.neon 444ac5895f Update phpstan's baseline file 6 years ago
phpstan.neon bbbb505da4 Remove merge markers. 6 years ago
phpunit.xml.dist 0fcbe868b0 Merge branch '3.next' into 4.x 6 years ago
psalm-baseline.xml db5edc9daa Fix errors reported by static analyzers 6 years ago
psalm.xml 8562214020 Fix errors reported by static analyzers. 6 years ago

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.