暂无描述

Mark Story 9860a554ae Add backwards compatibility mode for get() 9 年之前
.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 9860a554ae Add backwards compatibility mode for get() 9 年之前
tests 9860a554ae Add backwards compatibility mode for get() 9 年之前
.editorconfig e2bf915d0d Update editorconfig, supress warnings in Travis build, set cakephp-codesniffer to dev-master 11 年之前
.gitattributes 771643499c Update .gitattributes 9 年之前
.gitignore cbe6efa7ee Add phpcs.xml to gitignore 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 56c279ca29 Merge branch '3.next' into 3next-small-tiny-int 9 年之前
.varci.yml 3e0b3818b2 Improve version check regex 9 年之前
LICENSE.txt 3e07ab6812 Update LICENSE.txt 9 年之前
Makefile f9ff4cd4f2 Clean before building packages. 9 年之前
README.md fe1d812c89 Update URL in *.md, *.json 9 年之前
VERSION.txt c349d99651 Update version number to 3.4.3 9 年之前
appveyor.yml 96418aea67 Add WinCache 9 年之前
composer.json fe1d812c89 Update URL in *.md, *.json 9 年之前
phpcs.xml.dist 946478e7a1 Update backwards compat alias generation. 9 年之前
phpstan.neon e9a31f7ce6 More missing properties 9 年之前
phpunit.xml.dist a67e549203 Add support for PHPUnit6 in the Cake\TestSuite 9 年之前

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