Bot releases are visible (Hide)
Published by helhum over 6 years ago
The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum over 6 years ago
The complete setup process has been rewritten from scratch.
Most apparently the output is now more compact and looks nicer.
What you can also grasp from the terminal cast above, is that it is now possible
to hand over all argument for the setup process as environment variables.
Here is the complete list of default environment variables:
TYPO3_INSTALL_DB_USER
TYPO3_INSTALL_DB_PASSWORD
TYPO3_INSTALL_DB_HOST
TYPO3_INSTALL_DB_PORT
TYPO3_INSTALL_DB_UNIX_SOCKET
TYPO3_INSTALL_DB_USE_EXISTING
TYPO3_INSTALL_DB_DBNAME
TYPO3_INSTALL_ADMIN_USER
TYPO3_INSTALL_ADMIN_PASSWORD
TYPO3_INSTALL_SITE_NAME
TYPO3_INSTALL_SITE_SETUP_TYPE
Just like in previous versions, if you use the --no-interaction
flag, only required arguments need to be set. For all optional arguments the default values will be used then.
Last but not least, the whole setup process is now defined in a Yaml file. This means adding new arguments or even completely new steps is a matter of changing configuration.
Overriding the default configuration file is possible by providing the path to your own file with the TYPO3_INSTALL_SETUP_STEPS
environment variable. In this file you can decide to either import the default configuration and amend it to fit your needs (e.g. using different environment variables names or even hard code know values), or create a completely customized setup workflow, or even run different setup steps in different scenarios.
We are very much looking forward to what you are going to build with this feature.
CommandDispatcher::createFromComposerRun()
API changed, so that the first Composer event argument is obsolete. Passing it anyway will continue to work, but is deprecated.The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum over 6 years ago
The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum over 6 years ago
extension:activate
commandThe full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum over 6 years ago
The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum over 6 years ago
--json
to configuration:set
commandtypo3cms EXTCONF/lang/availableLanguages '["de", "fr"]' --json
typo3cms configuration:set SYS/caching/cacheConfigurations/cache_pages/options '{"compression": true}' --json
--opt
for mysqldump
in database:export
commandbackend:createadmin
commandThe full change log can be examined on Github
The extension can be found at the TER release page.
The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum over 6 years ago
All commands can now be registered with:
"command:name" => [
// Command configuration
]
This includes also commands from command controllers.
Run level, booting steps, replaces, aliases and vendor name
are now part of this configuration. All these are optional
with proper defaults in case they are missing.
Defaults are:
runLevel: full
booting steps: none
replaces: none
aliases: none
vendor name: package name (or extension key for TYPO3 extensions)
This allows to specify arbitrary aliases also for
command controller commands. Even different command names would be possible.
This also means, that aliases can be added as well to command controller commands.
Old registration and command controllers still work, as their registration is migrated to the new format.
Because this migrated configuration is merged with existing new configuration,
it is possible to just supply some command controller commands with aliases,
while not having to register every single command.
The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum over 6 years ago
The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum over 6 years ago
The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum over 6 years ago
The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum almost 7 years ago
typo3-console/composer-auto-setup
, when trying to setup a TYPO3 instance within a composer install process.The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum almost 7 years ago
The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum almost 7 years ago
typo3-console/composer-auto-setup
to work againThe full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum almost 7 years ago
We're delighted to present the next generation of TYPO3 command line tooling.
For TYPO3 Console 5.0 the complete application layer (how commands are found and executed)
has been refactored to use Symfony Console.
This means TYPO3 Console 5.0 is faster, more consistent, more compatible and more future proof than ever before.
-h
ahich shows the help for a command (e.g. use typo3cms cache:flush -h
to see the help for the cache flush command)../typo3cms install:generatepackagestates
, you can now also type ./typo3cms i:gen
and Symfony will find-v
-v[vv]
option is now globally available to increase verbositytypo3
and typo3cms
). Since TYPO3 Console 5 has become a complete replacement for the TYPO3 built in command line layer, only typo3cms
is left.backend:createadmin
was introduced, which allows to add admin users to a TYPO3 instancePHP_INI_PATH
environment variable.And many more cleanups, streamlining in the code base as well as the "UI" to make interacting with and creating new commands a more pleasant experience.
The good news here is, that the majority of commands will work just like before!
Nevertheless some things needed to be changed in a way that could break current workflows, scripts or commands.
The most important change is, that PHP 5 and TYPO3 7.6 will not be supported with TYPO3 Console 5.
If you need these, you can still use version 4.9.x, which is still maintained and will receive bugfixes, but no new features any more.
install:setup
typo3
binary is not installed with Composer any more (you won't need it anyway when using TYPO3 Console)database:export
now calls mysqldump
with option --single-transaction
. This means if you need a consistent state of the dump, make sure all your tables use InnoDB engine (not MyIsam).A few things are deprecated, which means they still work, but won't work any more in the next major release of TYPO3 Console.
E.g. arguments as options:
extension:activate --extension-keys foo,bar
is deprecated. Use extension:activate foo,bar
instead.
E.g. options as arguments:
cache:flush 1
is deprecated. Use cache:flush --force
instead
extension:activate
and extension:deactivate
are deprecated when TYPO3 is Composer managed (Composer mode). Use install:generatepackagestates
to generate the active list of extensions automatically from the composer installed extensions and then extension:setupactive
to set all active extensions up in your TYPO3 instance.extension:removeinactive
is deprecated. Only install the extensions you need, instead of installing the code and removing it afterwards.install:setup
the option --non-interactive
is deprecated. Use the global option --no-interaction
insteadinstall:generatepackagestates
the option --activate-default
is deprecated for Composer managed TYPO3. Instead require the TYPO3 core extensions you need in your project using composer.scheduler:run
the option --task-id
is deprecated. Use --task
instead.The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum almost 7 years ago
extension:dumpautoload
commandupgrade:all
command, which caused it to fail with upgrade wizards that download and install extensionsThe full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum almost 7 years ago
extension:dumpautoload
a low level commandThe full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum about 7 years ago
cache:flush
command when being executed low leveldatabase:updateschema
The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum about 7 years ago
This release marks the feature freeze of the 4.x branch of TYPO3 Console. All new features will only be implemented in the upcoming 5.x versions. Necessary bugfixes will be added to 4.9.x versions however.
--skip-extension-setup
for install:setup
command. This option is enabled by default in non composer setups. The installation finishes with all TYPO3 core extensions set up that are marked as required and as factory default. All local extensions are marked as inactive. Don't use this option in composer setups, when you want the setup to exactly reflect the defined state (all required core extensions active and all third party extensions are active).The full change log can be examined on Github
The extension can be found at the TER release page.
Published by helhum about 7 years ago
cache:flush
commandThe full change log can be examined on Github
The extension can be found at the TER release page.