PUBLIC MARKS from kasi77 with tags plugin & symfony

The sfStatsPlugin provides an easy way to display charts based on data you already own. Whether you want to follow the global progress of your application usage, or to analyze precisely how many specific actions were done by users under particular conditions, this plugin is for you. Based on a simple YAML configuration file, the plugin will take advantage of the methods from your Propel Object Model to display a nice line chart from Google Chart API or a jQuery flot.

The sfAdvancedConstPlugin is a symfony plugin that provides app wide constants functionality. It automatically generates constant values based on sfRefTable values and make them accessible in every app module. It works the following way - go through the tables defined in sfRefTable and generate for each id / name pair from this table constants. This plugin is different from sfConst plugin which required to keep all the constants directly in sfConst table and did not require ref tables. Effectively, both plugins are usefull to be used. Installation

The sfSyncClusterPlugin introduces a symfony sync-cluster task. The symfony sync-cluster task is intended as a replacement for the symfony sync task. While the plugin is backwards-compatible with symfony sync (they even use the same configuration files) this plugin offers several advantages over a traditional symfony sync. The symfony sync-cluster task: * Synchronizes a Symfony application across an unlimited number of servers. Symfony's sync only works for a single server. * Clears the Symfony cache on each server with a symfony cc. Doing this with sync requires an additional command. * Allows you to use ssh public/private keyfile authentication so you won't be prompted for a password during long deployments. * Allows you to deploy your web assets to a CDN without having to copy your entire site. The sfSyncCluster currently supports standard rsync transfer and transfer to Amazon S3. * Allows you to specify groups of servers to sync. If you have many servers, you can place them into logical groups and move them around quickly.

You will probably need to reuse a piece of code that you developed for one of your symfony applications. If you can package this piece of code into a single class, no problem: Drop the class in one of the lib/ folders of another application and the autoloader will take care of the rest. But if the code is spread across more than one file, such as a complete new theme for the administration generator or a combination of JavaScript files and helpers to automate your favorite visual effect, just copying the files is not the best solution