* The GitHub Organisation to work together: \url{https://github.com/TYPO3-Surf-CMS} **Ideas target specific configuration:** * Configuration/<ApplicationContext>/Settings.php * \url{https://github.com/AOEpeople/EnvSettingsTool} or HostConfiguration.php **Ideas DB Deployment** * set deleted=5 ... set deleted=timestamp (for currently deployed records) * pages / tt\_content complete sql * Configuration for specific tables? * Raise UID on live System * content\_deployment on forge? * uuid **Necessary tasks for TYPO3 CMS Deployments** * Kickstart Flow Package TYPO3SurfCms.SurfTools * Tasks needed for Stages * Initialize * More Flexible Directory Structure creation (e.g. using the generic directory task) * Package * composer packaging for TYPO3 CMS * (Maybe compile sass/less/js? use shell task!) * Transfer * (maybe scp/sftp) * scp ( I look) * Symlink Data (DONE) * Update * * Migrate * Database Migration (DONE) * Create Migration Strategy similar to doctrine migrations * Finalize * * Test * * Switch * Clear Cache (DONE) * Cleanup * Extend TYPO3CMS Application with necessary tasks for workflow * Default Workflow: local package, rsync transfer * Package type composer * Define / discuss deployment repo / distribution package structure * Clear Cache * db compare (live database or something smarter?) * Cache warmup * Curl Test * remove inactive packages from package states in production * remove inactive packages from directory structure during packaging **Unsorted ideas** * auto "install" exts if package states changed * auto detect changes in SQL files classes files or tca files and act accordingly * real path when warming up class caches (eg with own caching backend) * \url{https://github.com/AOEpeople/EasyDeploy} * \url{https://github.com/AOEpeople/EasyDeployWorkflows}