croogo's Introduction

Croogo

Croogo is a free, open source, content management system for PHP, released under MIT License.

It is powered by CakePHP MVC framework.

Requirements

Apache with mod_rewrite
PHP 5.3 or higher
MySQL 4.1 or higher

Installation

Installation using composer

The preferred way to install Croogo is by using composer.

composer create-project croogo/app myapp
cd myapp
composer install

Web based installer

Extract the archive. Upload the content to your server.
Create a new MySQL database (utf8_unicode_ci collation)
visit http://your-site.com/ from your browser and follow the instructions.

Manual installation

Extract the archive. Upload the content to your server.
Locate your app directory, and rename the following files:
- config/database.php.install to database.php, and edit the details.
- config/croogo.php.install to croogo.php, and edit the details.
- config/settings.json.install to settings.json
You can access your admin panel at http://your-site.com/admin. The installer should display a page for you to create the administrative user.

Installation using git

Beginning version 2.0.0, Croogo has been updated to be installed as a vendor package. This is intended to ease integration with an existing cakephp application.

Ensure you have a recent cakephp version 2.5
Run the following commands:

git clone git://github.com/croogo/app app && cd app && Console/add_submodule
If you intend to modify the default administration theme, you will need to regenerate the assets by running the following command from the application root directory:

Console/cake croogo make

The above command will fetch twitter bootstrap and FontAwesome and subsequently compile the CSS assets using lessphp.

Alternatively, you could use lessc or recess as the compiler as they generate a better result. Edit the COMPILE value in the Makefile accordingly and run:

( cd Vendor/croogo/croogo/Croogo ; make )

Contributors

Watchers

croogo's Issues

Get rid of CroogoAppController

It would be better to create a Component which can be included in the app's AppComponent. This way Croogo is able to act more like a actual plugin.

Automatic routing

Currently we create static routes for all routes we need, but this needs to be automatically, like in the past.

Remove all <Plugin>AppControllers

It's no longer necessary to have for example a UsersAppController. These can be removed from all plugins.

Create a HookableBehavior to handle hooking

It would be nice to create a HookableBehavior. This behavior would handle the hooking of behaviors using Croogo::hookBehavior(). This way there's no need to extend a central CroogoTable but its still possible to easily support extension using hooks.

Recommend Projects