Releases: TYPO3/Surf
Releases · TYPO3/Surf
Release 2.0.0-beta9
Release 2.0.0-beta8
TYPO3 Surf 2.0.0 beta7
Changes since Surf 2.0.0 beta6
Breaking changes:
- Flow default version is now 3.0. Set a different version in your deployment for older versions.
- For TYPO3 CMS tasks, the
applicationWebDirectory
andapplicationRootDirectory
have been removed. A new optionwebDirectory
was introduced which defaults toweb
- Surf now seamlessly integrates with newer versions of TYPO3 Console. However if you do not use a composer installation with default values, you need to set the path to the
typo3cms
binary in your configuration. e.g.$application->setOption('scriptFileName', './typo3cms');
Features
- The
surf describe
command was improved and now shows more detailed information on the deployment
Other changes
- Some minor documentation improvements and bugfixes.
TYPO3 Surf 2.0.0 beta6
Changes since Surf 2.0.0 beta4
- composer install task now uses authoritative class map
- fixed bug in clear opcode cache script generation
- use Flow utiltiy package in favor of symfony/finder and use it as well for better path calculations
Changes since Surf 2.0.0 beta5
- fix create directories task for Flow applications
TYPO3 Surf 2.0.0 beta5
Changes since Surf 2.0.0 beta4
- composer install task now uses authoritative class map
- fixed bug in clear opcode cache script generation
- use Flow utiltiy package in favor of symfony/finder and use it as well for better path calculations
TYPO3 Surf 2.0.0 beta4
Changes since Surf 2.0.0 beta3
- Fixed a missing escaping in DatabaseDumpTask
- Redirect stderr to stdout in Composer InstallTask. This fixes the annoying and misleading red warning output during deployments
TYPO3 Surf 2.0.0 beta3
Changes since Surf 2.0.0 beta2
This version includes some important bugfixes for TYPO3 CMS deployment.
Update to beta3 is recommended.
TYPO3 Surf 2.0.0 beta2
Changes since first beta release
The new Surf version contains a lot of bugfixes, cleanups and added features since the last release.
Added features
- Self update command for phar. Updating will become much easier. Just type
surf.phar self-update
and your phar will be automatically updated if a newer version is available. Since this is the first release with this feature, you'll have to download the phar one last time - Refinements for the TYPO3 CMS deployment workflow
** Extensions that are added will automatically be set up (database tables, configuration, static data, files) typo3_console version 2.0.0 or higher will be required
** DatabaseCompare task can now handle the typo3_console command for that action. No coreapi extension required- - Exclude flags for rsync transfer are now configurable. Example
$application->setOption('\TYPO3\Surf\Task\Transfer\RsyncTask[rsyncExcludes]' = ['.git', '.surf'];
- Private key can be specified for ssh connection $node->setOption('privateKeyFile' = 'path/.ssh/key';`
TYPO3 Surf - Flexible PHP Deployment
This is the first version of TYPO3 Surf, which runs completely standalone and is delivered as surf.phar binary for easy usage.
Work done compared to 0.9.0 release:
- Remove dependency to Flow and replace with smaller components that are needed (symfony/console ...)
- Changed the custom task identifier syntax to well know class name syntax (tasks are always referenced with full namespace when adding tasks or options. defined tasks should follow a similar convention, but still work the with arbitrary identifiers in case the base task is specified with full namespace.
- Added migration command for old deployment definitions
- Added specific TYPO3 CMS tasks and application (in the future I could imagine having these in an additional composer package)
- Tests are cleaned up and run on travis
- Documentation file is moved to markdown README
- Deployment definitions are looked for in $PWD/.surf or ~/.surf/deployments/
- surf.phar
Open TODOs for upcoming releases:
- Further cleanup README file
- Write more documentation
- Make the default deployment case (composer + dotenv) possible with (almost) zero configuration
- Add "setup" command to set deployment up on remote nodes (basically use a different set of tasks for that)
TYPO3 Surf - Flow Package
This is the version of TYPO3 Surf, as it is know by existing users. It requires TYPO3 Flow to work properly.
Users of this Surf Version are advised to change their composer.json
file from "typo3/surf": "dev-master"
to "typo3/surf": "~0.9.0"
as the code in master branch will change significantly soon.