Concrete console utility.

v0.0.9 2021-07-13 03:15 UTC

This package is auto-updated.

Last update: 2021-07-13 03:16:31 UTC



A command line utility for working with Concrete CMS.


Global Installation

The concrete console cli tool is meant to be installed globally with composer

composer global require concrete5/console

If you haven't already, make sure to add the global composer bin directory to your PATH.

export PATH=~/.composer/vendor/bin:$PATH

Running Commands

You can run commands just like this

concrete info

Which should get you something like:

# Location
Path to installation: /path/to/my/project/public
# concrete5 Version
Installed - Yes
Core Version - 8.5.4
Version Installed - 8.5.4
Database Version - 20200609145307

If you want to run a command against a different site, or if you've installed the console utility globally, any command that operates against a particular Concrete installation also has an --installation option (or -i for short.)

concrete info --installation=/path/to/my/site


# Location
Path to installation: /path/to/other/site/web
# concrete5 Version
Installed - Yes
Core Version - 8.5.0
Version Installed - 8.5.0
Database Version - 20190301133300


The most important items we want to currently focus on are:

  • Add the ability to dump sites, configurations, files and more into a standardized backup archive.
  • Add the ability to restore a Concrete site from one of these standardized backup archives, by passing a file to a given concrete restore my_backup.gz command.
  • Improved stability of backup and restore
  • Restore into an uninstalled concrete5
  • Backing up a version 6 site

After that, we'd be happy to add as many features as you'd like. Should this tool include the ability to create boilerplate block or package code? Absolutely! Should we move code sniffer and code fixing functionality from the core console command to this tool? Yes, please.


Why is this tool not built into the core?

We wanted a unified, standardized place to offer a devops and developer's toolkit. The core didn't seem like a great place for it. We want to be able to iterate on this quickly, which means not tying releases of this console utility to releases of the core.

Is this tool meant to replace the concrete5 utility that ships with the core?

I don't know yet. Perhaps in the long term, yes – but that seems like an awful lot of work. Let's just focus on making this tool augment and improve the tools around Concrete CMS, and slowly sunset the original console utility that's built into the core.