No Description

mscherer 514b961498 Fix up class usage. 7 years ago
.github fe1d812c89 Update URL in *.md, *.json 9 years ago
config 075cd238bb Merge branch '3.next' into 4.x 7 years ago
contrib 6314160643 Remove explicit standard from phpcs command. 7 years ago
src a7a406f503 Update return type of log adapters. 7 years ago
templates 38abe4e02a Rename MissingCellViewException to CellTemplate 7 years ago
tests 514b961498 Fix up class usage. 7 years ago
.editorconfig e2bf915d0d Update editorconfig, supress warnings in Travis build, set cakephp-codesniffer to dev-master 11 years ago
.gitattributes 4feee54636 Fix typo 7 years ago
.gitignore 8e5a24bf6e Ignore composer.phar 7 years ago
.mailmap bbcbcedde9 Update .mailmap 8 years ago
.scrutinizer.yml 20a4e57a42 Add .scrutinizer.yml 10 years ago
.stickler.yml f01c2cfc86 Use relative paths in phpcs configuration. 7 years ago
.travis.yml 465edec4d9 Use phpstan level 3 by default. 7 years ago
.varci.yml e38c1eca08 Var.CI should accept `composer show` output 7 years ago
LICENSE 1d36e9fbc5 Update LICENSE 7 years ago
Makefile f7f5f4331f Add branch cleanup task to makefile. 9 years ago
README.md 499acb38e2 Remove version number from composer require command 7 years ago
VERSION.txt b1097d0d29 Start 4.x branch. 8 years ago
appveyor.yml 04ff0041c3 Always download composer.phar 7 years ago
composer.json c96b280700 Merge pull request #12951 from cakephp/4.x-stub2 7 years ago
phpcs.xml.dist 35e4ff6688 Remove unneeded exclusion in phpcs config. 7 years ago
phpstan.neon 848d6872c6 Fix error reported by phpstan. 7 years ago
phpunit.xml.dist e9f73b8ccb Fix phpunit.xml validation error. 7 years ago
psalm.xml cb84d2812b Fix few errors reported by static analysers. 7 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.