No Description

stickler-ci 93b4a6c404 Fixing style errors. 7 years ago
.github fe1d812c89 Update URL in *.md, *.json 9 years ago
config ead58dffb9 Update CA bundle to 2018-10-17 7 years ago
contrib 79771590f1 Add linting as suggested by @jrbasso 11 years ago
src 93b4a6c404 Fixing style errors. 7 years ago
tests d6d3fda11b Try to fix aggregate test for SQLServer. 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 c73bed8100 true. 8 years ago
.mailmap bbcbcedde9 Update .mailmap 8 years ago
.scrutinizer.yml 20a4e57a42 Add .scrutinizer.yml 10 years ago
.stickler.yml 1b8a8c8eb4 Enable automatic PHPCS fixing from stickler 8 years ago
.travis.yml eef876ce0e Use PHP 7.3 alias. 7 years ago
.varci.yml e38c1eca08 Var.CI should accept `composer show` output 7 years ago
LICENSE 88fa014289 This should make it pick up 8 years ago
Makefile f7f5f4331f Add branch cleanup task to makefile. 9 years ago
README.md a3852b4675 Update README.md 8 years ago
VERSION.txt cb3034e636 Update version number to 3.6.12 7 years ago
appveyor.yml e0db18ff24 Always download composer.phar 7 years ago
composer.json 45c1015e9c Merge branch 'master' into 3.next 8 years ago
phpcs.xml.dist 946478e7a1 Update backwards compat alias generation. 9 years ago
phpstan.neon e119be2769 Update phpstan config. 7 years ago
phpunit.xml.dist d4010d4bd9 Merge branch 'master' into 3.next 8 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:"~3.6"

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.