<div dir="ltr">Hi Simon,<div><br></div><div>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...)</div><img width="0" height="0" class="mailtrack-img" src="https://mailtrack.io/trace/mail/1c64ca525030a5a8ef10747140ac5b101c64d6e3.png"></div><div class="gmail_extra"><br><div class="gmail_quote">2015-03-18 14:47 GMT+01:00 Loek Hilgersom <span dir="ltr"><<a href="mailto:loek@netcoop.nl" target="_blank">loek@netcoop.nl</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Simon,<br>
<br>
You can find my deployment scripts here, maybe you get a few ideas from that:<br>
<a href="https://github.com/netcoop/typo3-installer" target="_blank">https://github.com/netcoop/<u></u>typo3-installer</a><br>
<br>
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.<br>
<br>
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).<br>
<br>
Hope it helps you somehow, I'd be happy to be involved in further discussions/developments on this sort of thing.<span class="HOEnZb"><font color="#888888"><br>
<br>
Loek</font></span><span class="im HOEnZb"><br>
<br>
<br>
On 18-03-15 11:28, Simon Schaufelberger (Schaufi) wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
I have done a lot of research about deploying a TYPO3 cms website for many<br>
months already but when it comes to deploying TYPO3 cms, I wish there would be<br>
more "Inspiring people to share" ;) I hope I can inspire people to share a bit<br>
now! :D<br>
<br>
I want to have a continuous deployment with files and database but without<br>
deploying "everything" for every release since that's quite a lot of data that<br>
needs to be copied.<br>
<br>
For the files to sync I use git but the database is really difficult since the<br>
database is changed (only) on the dev machine and then exported (with mysqldump)<br>
and imported on live again. The big problem here is the few seconds of downtime<br>
during deployment when the tables are deleted and imported again. I would like<br>
to have a system without any "broken state".<br>
<br>
What I'm looking for is a proper way to:<br>
- copy database (export, rename, import)<br>
- import new data into new database with mysql import<br>
- switch database somehow (maybe through symlink change in<br>
LocalConfiguration.php ?). Another idea: Is there a way to use and change<br>
environment variables somehow so that I can tell TYPO3 which database to use?<br>
<br>
PS: I have written a deployment extension that runs with the scheduler and<br>
performs shell scripts so in the end I want a shell script ;)<br>
</blockquote></span><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
Before posting to this list, please have a look to the posting rules<br>
on the following websites:<br>
<br>
<a href="http://typo3.org/teams/core/core-mailinglist-rules/" target="_blank">http://typo3.org/teams/core/<u></u>core-mailinglist-rules/</a><br>
<a href="http://typo3.org/development/bug-fixing/diff-and-patch/" target="_blank">http://typo3.org/development/<u></u>bug-fixing/diff-and-patch/</a><br>
______________________________<u></u>_________________<br>
TYPO3-team-core mailing list<br>
<a href="mailto:TYPO3-team-core@lists.typo3.org" target="_blank">TYPO3-team-core@lists.typo3.<u></u>org</a><br>
<a href="http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core" target="_blank">http://lists.typo3.org/cgi-<u></u>bin/mailman/listinfo/typo3-<u></u>team-core</a><br>
</div></div></blockquote></div><br></div>