Download the PHP package exs/terminal-bundle without Composer

Symfony 2.x TerminalBundle

Terminal bundle to log all command output regardless of output buffer (echo / print_r / var_dump / ->ln()), lock commands to prevent them from running concurrently, provide command stats (pid, runtime, errors) and log any exceptions / errors in the database. Very useful for controlling commands via web interface when commands are being run via cronjob. Handles legacy code that was ported tyo your symfony2 app quick and dirty.

Bundle is installed as a service listening for all exceptions and logging them in the database. Locks use the command alias as the slug for ease of reference. When used in conjunction with a crontab enabled monitor we can then alert the dev team when there are errors, current lock hits, and review the logs via web interface instead of having to login to the particular host that had the problem.

Options

Installing the TerminalBundle in a new Symfony2 project

So the TerminalBundle is ready for installation, great news but how do we install it. The installation process is actually very simple. Set up a new Symfony2 project with Composer.

Once the new project is set up, open the composer.json file and add the exs/terminal-bundle as a dependency:

Save the file and have composer update the project via the command line:

Composer will now update all dependencies and you should see our bundle in the list:

Update the app/AppKernel.php and app/config/routing.yml to include our bundle, clear the cache and update the schema:

You have to manually update the db with doctrine:schema:update console command.

Migrations won't work because they need the table that they're going to create...

Lastly, copy the including bash file: "runner" from the vendor/exs/terminal-bundle/EXS/TerminalBundle/runner to app/runner That adds the hooks into the original console script without altering the original.

Make sure you're mailer is properly configurated in config.yml and in parameters.yml:

and now you're done.

If you want to test them try opening up the same command in two terminals simultaneously. They currently run for 3 seconds each:

Once you're run the above command you will be able to verify everything worked by checking the database. The locks and logs will be logged in your database in the following tables:

• terminallogs

• commandlocks

Additionally if your command exited with a non 0 status it likely logged an exception in the exception5xx table.

Contributing

Anyone and everyone is welcome to contribute.

If you have any questions or suggestions please let us know.