[TYPO3-core] TYPO3 CMS Deployment with code and database

[Jose Antonio Guerra]

Hi Simon,

Why do you need to rewrite the DB data on every deploy? Deployments besides
initial installation should only change the codebase, not the assets
(uploads, db) which should be unique for every environment (dev, staging,
prod...)

2015-03-18 14:47 GMT+01:00 Loek Hilgersom <loek at netcoop.nl>:

> Hi Simon,
>
> You can find my deployment scripts here, maybe you get a few ideas from
> that:
> https://github.com/netcoop/typo3-installer
>
> I have presented this at T3dd12 and the scripts have been updated and
> improved since, although I'd do it slightly different if I would do it
> again.
>
> Average deployment takes me between 15 and 30 seconds, of which there is
> hardly any real downtime. I don't remove tables to import them again, just
> using deltas (mostly update queries).
>
> Hope it helps you somehow, I'd be happy to be involved in further
> discussions/developments on this sort of thing.
>
> Loek
>
>
> On 18-03-15 11:28, Simon Schaufelberger (Schaufi) wrote:
>
>> Hello,
>> I have done a lot of research about deploying a TYPO3 cms website for many
>> months already but when it comes to deploying TYPO3 cms, I wish there
>> would be
>> more "Inspiring people to share" ;) I hope I can inspire people to share
>> a bit
>> now! :D
>>
>> I want to have a continuous deployment with files and database but without
>> deploying "everything" for every release since that's quite a lot of data
>> that
>> needs to be copied.
>>
>> For the files to sync I use git but the database is really difficult
>> since the
>> database is changed (only) on the dev machine and then exported (with
>> mysqldump)
>> and imported on live again. The big problem here is the few seconds of
>> downtime
>> during deployment when the tables are deleted and imported again. I would
>> like
>> to have a system without any "broken state".
>>
>> What I'm looking for is a proper way to:
>> - copy database (export, rename, import)
>> - import new data into new database with mysql import
>> - switch database somehow (maybe through symlink change in
>> LocalConfiguration.php ?). Another idea: Is there a way to use and change
>> environment variables somehow so that I can tell TYPO3 which database to
>> use?
>>
>> PS: I have written a deployment extension that runs with the scheduler and
>> performs shell scripts so in the end I want a shell script ;)
>>
> _______________________________________________
> Before posting to this list, please have a look to the posting rules
> on the following websites:
>
> http://typo3.org/teams/core/core-mailinglist-rules/
> http://typo3.org/development/bug-fixing/diff-and-patch/
> _______________________________________________
> TYPO3-team-core mailing list
> TYPO3-team-core at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20150318/2ac6a46f/attachment-0001.htm>