Timeline for Using version control (Git) on a MySQL database
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 11, 2021 at 17:25 | answer | added | stPatrick | timeline score: 1 | |
| Dec 28, 2015 at 8:23 | history | edited | Palec | CC BY-SA 3.0 |
Reduced fluff, removed irrelevant [wordpress]
|
| Nov 24, 2014 at 15:06 | answer | added | Anonymous | timeline score: 0 | |
| Jul 13, 2014 at 3:18 | answer | added | Kevin | timeline score: 8 | |
| Jun 26, 2013 at 13:38 | answer | added | abanmitra | timeline score: 6 | |
| Apr 6, 2013 at 22:37 | vote | accept | Zach Russell | ||
| Dec 3, 2012 at 18:42 | answer | added | Kevin A. Naudé | timeline score: 24 | |
| Nov 29, 2012 at 14:56 | comment | added | Svend Hansen | I did a quick google for "Wordpress Version Control" and found this list of Wordpress plugins: wordpress.org/extend/plugins/tags/version-control Would any of them be useful? | |
| Nov 28, 2012 at 15:45 | comment | added | Christian |
Also, you could keep the database checked into a develop branch, and use the technique here to exclude the database from being merged into master. Then only deploy from master. In theory, that should work.
|
|
| Nov 28, 2012 at 15:43 | comment | added | Christian | I dump the database and check it into version control. But I don't push to the server on Wordpress projects (git isn't always available on shared hosting). So generally I upload manually via FTP, as bad as that is. Interested to hear some proper practices when using git to deploy. | |
| Nov 28, 2012 at 15:35 | history | asked | Zach Russell | CC BY-SA 3.0 |