説明なし

Marc Würth 5f598fc4ad Let Stickler CI ignore the 2.x related branches 9 年 前
.github f93f0850fa Remove unneeded headings. 10 年 前
config 343e206360 Re-add the Equifax Secure Certificate Authority 10 年 前
contrib 79771590f1 Add linting as suggested by @jrbasso 11 年 前
src 7798ad50ef Merge pull request #8989 from ravage84/space-before-object-operator 9 年 前
tests 2af2dc8c36 Add in some brackets 9 年 前
.editorconfig e2bf915d0d Update editorconfig, supress warnings in Travis build, set cakephp-codesniffer to dev-master 11 年 前
.gitattributes 5cdc7c0eef Remove non existant bake. 11 年 前
.gitignore cbe6efa7ee Add phpcs.xml to gitignore 9 年 前
.scrutinizer.yml 20a4e57a42 Add .scrutinizer.yml 10 年 前
.stickler.yml 5f598fc4ad Let Stickler CI ignore the 2.x related branches 9 年 前
.travis.yml 44e44bc35c No need to install apcu_bc on travis. 9 年 前
LICENSE.txt 6fd1cbbc68 Update license year 10 年 前
Makefile 95329be57b Fix makefile for building non-head packages. 10 年 前
README.md ee858fadd5 Remove unstable branch badge. 9 年 前
VERSION.txt f8f48386f7 Update version number to 3.2.10 9 年 前
appveyor.yml 5def525cb4 update the checked branch name 10 年 前
composer.json b79d8131fc Add Security::random() 10 年 前
phpcs.xml.dist 9f7334b25f Rename phpcs.xml to phpcs.xml.dist and fix slashes in path. 9 年 前
phpunit.xml.dist 7c1b694bd2 Exclude ctp files from coverage. 10 年 前

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

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

CONTRIBUTING.md - Quick pointers for contributing to the CakePHP project.

CookBook "Contributing" Section - Details about contributing to the project.

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.