The Aimeos Flow package provides some commands that can be executed from the command line shell. These commands are available:
Technically, they are implemented as Flow command controllers which can be executed from the base directory for your TYPO3 Flow application via:
./flow aimeos:<name> ...
For best performance, Aimeos caches the generated HTML of the components as long as the cache manager configuration option isn't set to "None". The cached HTML snippets are invalidated if their content is changed but sometimes you might want to clear the complete cache at once:
./flow aimeos:cache [<site>]
The aimeos:cache command accepts an optional site code or list of site codes separated by white spaces. If no site code in given, the content caches of all sites are cleared.
Running a shop requires several tasks that need to be executed regularly like sending notification e-mails, update the catalog index or export orders to the ERP system. The "aimeos:jobs" command is able to perform these task by calling the appropriate core job controllers. More details about the required jobs and their setup is available in the article about configuring the cronjobs.
./flow aimeos:jobs <jobs> [<site>]
At least one job name is required but you can hand over several job names at once if you separate them via white spaces. By executing ./flow help aimeos:jobs, the jobs controller displays the available jobs and their meaning.
The aimeos:jobs command accepts an optional site code or list of site codes separated by white spaces. If no site code in given, the jobs are executed for all sites.
To execute the setup tasks for creating or updating the Aimeos database structure use:
./flow aimeos:setup [--option="..."] [<site>]
You can pass additional options to the setup tasks using the "--option=..." command line switch. If options require a value, the option name and value is separated by an colon (":"). Currently available is the following setup option:
The aimeos:setup command accepts an optional site code or list of site codes separated by white spaces. If no site code in given, the "default" site is assumed.