No Description

Mark Story a7bedf10bb Set max PHP version. 5 years ago
.github 11d85302e2 Improve wording, grammar, punctuation etc. 5 years ago
config 7c79b9e99c Backports from 4.next. 5 years ago
contrib 79771590f1 Add linting as suggested by @jrbasso 11 years ago
src 6d488df680 Merge pull request #14909 from zoghal/3.x-patch-pj() 5 years ago
tests b5c3bff366 Remove trailing whitespace 5 years ago
.appveyor.yml 8299c27cc2 Merge 3.x into 3.next 5 years ago
.editorconfig 5749a812b5 Add identation style for Makefile to .editorconfig 6 years ago
.gitattributes 90d412c43e Merge pull request #14014 from othercorey/remove-varci 6 years ago
.gitignore 96ee5cbadd Merge remote-tracking branch 'origin/master' into 3.next 6 years ago
.mailmap 266f1c9f27 Update .mailmap 6 years ago
.scrutinizer.yml 20a4e57a42 Add .scrutinizer.yml 10 years ago
.stickler.yml 2286694743 Added 3.next to disabled list. 5 years ago
.travis.yml e728f03195 Update Xcache URL 5 years ago
LICENSE 1d36e9fbc5 Update LICENSE 7 years ago
Makefile 272ea5e837 Remove unnecessary guard. 5 years ago
README.md a96483bc60 Update README.md 6 years ago
SECURITY.md 62911c86ee Adding SECURITY.md 6 years ago
VERSION.txt 74f60e2e1f Update version number to 3.9.3 5 years ago
composer.json a7bedf10bb Set max PHP version. 5 years ago
phpcs.xml.dist 3f0bdd6ff3 Exclude TODO sniff for 3.next development 7 years ago
phpstan.neon f370ea00f7 Fix phpstan. 5 years ago
phpunit.xml.dist b2f53ed625 Remove outdated configs 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.