I have been responsible for updating a number of CakePHP applications lately, and needed to delete the cache files every time I did a 'git pull' on the server. I couldn't find any existing shell that takes care of a task like this, so decided to write one quickly.
What it doesAt the moment, the plugin deletes each and every file in /app/tmp with a prefix 'cake_'.
How to use it?You have to to use it from CakePHP console for now. If I have time later, may be I will make it a Croogo supported plugin so that cache files can be deleted from admin panel too.
$ ./cake clear_cache all
Get it from GitHub here: https://github.com/fahad19/clear_cache.
Note: I just found out about another CakePHP plugin by Ceeram, and surprisingly it has the same name. I just wish I found it earlier: https://github.com/ceeram/clear_cache.
This is really a great news! I still remember reading that HotScripts newsletter a few years ago on my cellphone where I first learned about CakePHP framework. A few years later, Croogo was developed and today featured on HotScripts. It is really amazing to see how things connect.
I, on behalf of the growing Croogo community, thank HotScripts for recognizing this project and helping spread the word! :)
Croogo's documentation has been made open to all. Till now, the wiki is managed by me only but I am looking forward to some community contribution.
Want to help extend Croogo's documentation further? Developed a new plugin or theme, and want to list it in the wiki? Want to add your new Croogo powered website to the showcase? Fork the repository, make changes and send a pull request on GitHub!
GitHub address: http://github.com/croogo/documentation
Documentation itself is a git repository. Whatever you see inside the repository is made available in the wiki. Basically it is an organized collection of markdown formatted files. Can be downloaded for personal offline use too.
This whole process has led me to develop a new plugin called Gitwiki. This is the plugin that runs the Croogo wiki. It uses documentation repository as a Git submodule and takes care of processing the markdown files.
GitHub address: http://github.com/croogo/gitwiki
Questions may arise, why not let users log in to croogo.org, add/edit pages and submit for review/approval? Because, I don't want to take the pain of developing a full working wiki application with diffing and revisioning features, and also review the submissions at the end of the day one by one. Using a version control system like Git takes the pain way, and with GitHub everyone can see what others are up to by just looking at the network graph. And most of the people willing to contribute to Croogo's documentation are likely to be those with some technical knowledge. So using GitHub makes perfect sense.
At the moment, documentation is written in English only. But I have already received requests for supporting other languages too, and will be working on that in coming weeks (largely depends on how many translators are willing to help). API documentation could be up soon by using API Generator plugin too.
And oh, Croogo turns 1 tomorrow! :)