Download the PHP package pantheon-quicksilver/debugging-example without Composer
On this page you can find all versions of the php package pantheon-quicksilver/debugging-example. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download pantheon-quicksilver/debugging-example
More information about pantheon-quicksilver/debugging-example
Files in pantheon-quicksilver/debugging-example
Package debugging-example
Short Description Quick debugging example for users explore the potential of Quicksilver.
License MIT
Homepage https://github.com/pantheon-quicksilver/debugging-example
Informations about the package debugging-example
Quicksilver Debugging
This example is intended for users who want to explore the potential for Quicksilver with a quick debugging example.
Requirements
While these scripts can be downloaded individually, they are meant to work with Composer. See the installation in the next section.
- Quicksilver script projects and the script name itself should be consistent in naming convention.
- README should include a recommendation for types of hooks and stages that the script should run on.
- For example, "This script should run on
clone_databaseand theafterstage. - Provide a snippet that can be pasted into the
pantheon.ymlfile.
- For example, "This script should run on
Installation
This project is designed to be included from a site's composer.json file, and placed in its appropriate installation directory by Composer Installers.
In order for this to work, you should have the following in your composer.json file:
The project can be included by using the command:
composer require pantheon-quicksilver/debugging-example
If you are using one of the example PR workflow projects (Drupal 8, Drupal 9, WordPress) as a starting point for your site, these entries should already be present in your composer.json.
Example pantheon.yml
Here's an example of what your pantheon.yml would look like if this were the only Quicksilver operation you wanted to use.
Example terminus workflow:watch Output
Triggering cache clears from your dashboard you should enjoy nice debugging output like this:
The wf_type, wf_description and user_email values are likely to be of particular interest. You can get additional information from the $_SERVER and $_ENV superglobals. You can also interrogate the status of the git repository, as well as bootstrapping the CMS. There are lots of possibilities! Have fun with Quicksilver!