Plugin uninstall symfony

You could even set up your own plugin channel to easily install the plugins you've written yourself! To install plugins from the default channel the official symfony channel , it is no longer necessary to use the full URL to the packages to install them.

A simple command is now enough:. This will immediately install the sfGuardPlugin for you. However, there are more options available to control what gets installed into your project:. This will install a non-stable plugin into your project, which is useful if you either want to try out the beta of an already stable plugin, or if you want to try out this new plugin that does not have a stable release yet.

Various plugins are depending on other plugins to be installed before they can work. In symfony 1. To install a plugin and all it's dependencies, symfony issue the command:. No more browsing through various wiki pages to find all the install instructions and get everything working, symfony will now take care of the installation of those plugins for you.

Another improvement thanks to using PEAR channels is the ability to use several different channels. Another improvement thanks to using PEAR channels is the ability to use several different channels. By default, symfony uses the official symfony PEAR channel plugins. To use other channels, you will first need to add a new channel:. The above extra parameters all also have a shorthand notation, which can be found by using the help:.

And last but not least, it is also possible to directly reference the PEAR package of the plugin you want to install, either using a full URL or a local path:.

The task of uninstalling a plugin to remove it from your project is still very easy. One simple command will do the trick:. One thing to take note of though is if you use multiple channels, and you want to uninstall a plugin that comes from another channel than the default symfony-plugins channel, you need to specify the channel:.

To find out which channel a plugin is installed from, you can use the. If you want to upgrade a plugin, this is very simple. Just issue a single command and your plugin is up-to-date with the latest version:. The arguments --stability , --release and --channel , including their shorthand notations, are also available for this task and apply in the same way.

The generate:module task creates the basic directory structure for a new module in an existing application:. The task can also change the author name found in the actions. If a module with the same name already exists in the application, it throws a sfCommandException. The generate:project task creates the basic directory structure for a new project in the current directory:. If the current directory already contains a symfony project, it throws a sfCommandException.

The namespaceNameTask. Note that the namespace is optional. If you want to create the file in another directory relative to the project root folder , pass it in the --dir option. This directory will be created if it does not already exist.

If you want the task to default to a connection other than propel , provide the name of this connection with the --use-database option:.

The --use-database option can also be used to disable database initialization in the generated task:. The i18n:extract task extracts i18n strings from your project files for the given application and target culture:. By default, the task only displays the number of new and old strings it found in the current project. If you want to display strings that are present in the i18n messages catalogue but are not found in the application, use the --display-old option:. To automatically delete old strings, use the --auto-delete but be careful, especially if you have translations for plugins as they will appear as old strings but they are not:.

As the task returns all strings embedded in PHP, you can have some false positive especially if you use the string syntax for helper arguments. See plugin:install for more information about the format of the plugin name and options. The project::clear-controllers task clears all non production environment controllers:.

The project:clear-controllers task clears all non production environment controllers:. You can use this task on a production server to remove all front controller scripts except the production ones.

To automate the deployment, the task uses rsync over SSH. By default, the task is in dry-mode. To do a real deployment, you must pass the --go option:.

Last, you can specify the options passed to the rsync executable, using the rsync-options option defaults are -azC :. The project:unfreeze task removes all the symfony core files from the current project:. The project:upgrade1.