説明なし

ADmad 3824b474f0 Fix CS errors. 7 年 前
.github fe1d812c89 Update URL in *.md, *.json 9 年 前
config 075cd238bb Merge branch '3.next' into 4.x 7 年 前
contrib 6314160643 Remove explicit standard from phpcs command. 7 年 前
src 3824b474f0 Fix CS errors. 7 年 前
templates 7fbc5fef08 Update templates path in error page 7 年 前
tests 3824b474f0 Fix CS errors. 7 年 前
.editorconfig e2bf915d0d Update editorconfig, supress warnings in Travis build, set cakephp-codesniffer to dev-master 11 年 前
.gitattributes a978b04932 Ignore psalm files in git archive. 7 年 前
.gitignore 8e5a24bf6e Ignore composer.phar 7 年 前
.mailmap 266f1c9f27 Update .mailmap 7 年 前
.scrutinizer.yml 681b418238 Update scrutinizer as well 7 年 前
.stickler.yml f01c2cfc86 Use relative paths in phpcs configuration. 7 年 前
.travis.yml cd7cc5af28 Make PHP 7.2 the minimum required version for 4.x 7 年 前
.varci.yml e38c1eca08 Var.CI should accept `composer show` output 7 年 前
LICENSE 1d36e9fbc5 Update LICENSE 7 年 前
Makefile f7f5f4331f Add branch cleanup task to makefile. 9 年 前
README.md 499acb38e2 Remove version number from composer require command 7 年 前
VERSION.txt 98defb51d3 Update version number to 4.0.0-alpha1 7 年 前
appveyor.yml f36b69ffe3 Try to avoid installing PHP each time on appveyor. 7 年 前
composer.json 9e30b107c5 Don't update PHPUnit. 7 年 前
phpcs.xml.dist 35e4ff6688 Remove unneeded exclusion in phpcs config. 7 年 前
phpstan.neon f3483c1721 Update phpstan config 7 年 前
phpunit.xml.dist e9f73b8ccb Fix phpunit.xml validation error. 7 年 前
psalm-baseline.xml 8084aab8be Clean up the expected input scope. 7 年 前
psalm.xml 3407f56cc6 Ignore noisy psalm check. 7 年 前

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.