No Description

Mark Sch ecd2dfc212 Update .mailmap 9 years ago
.github 9fbf99a78b Improved wording 9 years ago
config c262b9ba4c Merge pull request #8771 from CVO-Technologies/model-factory-static 10 years ago
contrib 79771590f1 Add linting as suggested by @jrbasso 11 years ago
src 04ee27dda4 Improve descriptiveness of exception message 9 years ago
tests 8c61766e98 Fix options being passed down from validateUnique 9 years ago
.editorconfig e2bf915d0d Update editorconfig, supress warnings in Travis build, set cakephp-codesniffer to dev-master 11 years ago
.gitattributes abe9201d54 Remove metadata files from archived packages. 9 years ago
.gitignore cbe6efa7ee Add phpcs.xml to gitignore 9 years ago
.mailmap ecd2dfc212 Update .mailmap 9 years ago
.scrutinizer.yml 20a4e57a42 Add .scrutinizer.yml 10 years ago
.stickler.yml 5f598fc4ad Let Stickler CI ignore the 2.x related branches 9 years ago
.travis.yml 1d5b558e72 Pin apcu version to avoid segfault on travis 9 years ago
.varci.yml 3e0b3818b2 Improve version check regex 9 years ago
LICENSE.txt 6fd1cbbc68 Update license year 10 years ago
Makefile 95329be57b Fix makefile for building non-head packages. 10 years ago
README.md 8812850893 Updated cake version on readme 9 years ago
VERSION.txt 6ab9f76c5c Update version number to 3.3.8 9 years ago
appveyor.yml 5def525cb4 update the checked branch name 10 years ago
composer.json 489b5f8557 Add scripts for testing/checking. 9 years ago
phpcs.xml.dist 9f7334b25f Rename phpcs.xml to phpcs.xml.dist and fix slashes in path. 9 years ago
phpunit.xml.dist 7c1b694bd2 Exclude ctp files from coverage. 10 years ago

README.md

CakePHP Framework

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.3"

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.
  • 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 - Offical 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.