説明なし

Jeremy Harris 6d344eaf6d Cloning fallback and copying copyable config to it 8 年 前
.github fe1d812c89 Update URL in *.md, *.json 9 年 前
config c262b9ba4c Merge pull request #8771 from CVO-Technologies/model-factory-static 10 年 前
contrib 79771590f1 Add linting as suggested by @jrbasso 11 年 前
src 6d344eaf6d Cloning fallback and copying copyable config to it 8 年 前
tests 6d344eaf6d Cloning fallback and copying copyable config to it 8 年 前
.editorconfig e2bf915d0d Update editorconfig, supress warnings in Travis build, set cakephp-codesniffer to dev-master 11 年 前
.gitattributes 7f36b2c458 Do not ignore PHPStan files 9 年 前
.gitignore 28c5e0060f Ignore debug.log and error.log 9 年 前
.mailmap 9cab03c8c7 Update .mailmap 9 年 前
.scrutinizer.yml 20a4e57a42 Add .scrutinizer.yml 10 年 前
.stickler.yml 5f598fc4ad Let Stickler CI ignore the 2.x related branches 9 年 前
.travis.yml 1c4c644c08 Merge branch 'master' into 3.next 8 年 前
.varci.yml 3e0b3818b2 Improve version check regex 9 年 前
LICENSE.txt 3e07ab6812 Update LICENSE.txt 9 年 前
Makefile f7f5f4331f Add branch cleanup task to makefile. 9 年 前
README.md aa0785be42 Add the cake logo to the README 9 年 前
VERSION.txt b1aaa09489 Update version number to 3.4.7 8 年 前
appveyor.yml 96418aea67 Add WinCache 9 年 前
composer.json 243fc81448 Remvoe rest-api 8 年 前
phpcs.xml.dist 946478e7a1 Update backwards compat alias generation. 9 年 前
phpstan.neon 68d2fcb83f Fix some errors reported by phpstan level 2. 9 年 前
phpunit.xml.dist a67e549203 Add support for PHPUnit6 in the Cake\TestSuite 9 年 前

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

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.