Timeline for Private theme update with zip archive without deactivating the theme
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 3, 2015 at 23:01 | comment | added | Rarst | There are deployment tools that implement this principle (nothing I use myself since I don't need this degree of speed and stick with version control), but really it's trivial and can be done by hand with as little as your FTP client of choice. | |
| Dec 3, 2015 at 23:00 | comment | added | Rarst | But you don't need to with this method?.. You just upload whole current version of the theme. | |
| Dec 3, 2015 at 22:57 | comment | added | chestozo | What I am avoiding is: - calculating updated files since last update - uploading these files one by one (if they are in different directories let's say). But maybe your magic script does all this manual work. Is it open sourced? :) | |
| Dec 3, 2015 at 15:56 | comment | added | Rarst | Well, that's the best way to do it on your own server, so I am not sure what the "avoiding" is trying to prevent. :) | |
| Dec 3, 2015 at 15:46 | comment | added | chestozo | Thank you for your answer. But this is actually what I am trying to avoid. Was playing today with this plugin github.com/afragen/github-updater but it feels that it doesn't work properly with bitbucket ... ( | |
| Dec 3, 2015 at 11:12 | history | answered | Rarst | CC BY-SA 3.0 |