I’ve been building my themes using roots for a while now (and still loving it). My workflow has been…
- Host theme in bitbucket repo
- DeployBot monitors the repo and when it detects a commit, compiles the theme (eg dynamically creates /dist)
- DeployBot then deploys the relevant files to my server via FTP
The compilation of the theme upon each deployment has seemed like a necessary step in order to reproduce and overwrite the existing /dist folder on the server as opposed to merging changes (as a lot of the css/js is minified, I’ve thought this can get messy - correct me if I’m wrong).
I’m now getting to the point where DeployBot’s build tools often errors/fails, sometimes for no apparent reason (which is especially frustrating when I really need to get an update out). I need to adjust my workflow to something a little more stable. Of course I still want to utilise roots/gulp however not quite sure what the happy medium is so that I’m not compiling my theme each time upon deployment.
Can someone recommend something that works for them?