I’m using Roots 7.0 on a host where I Git Deploy (WPEngine). The new grunt workflow creates scripts, css and the manifest.json files, but all of those are commented out in .gitignore. Since they never make it in to my repo, they never get deployed when I push to the production servers. I assume the…

I haven’t check out Roots 7.0 but I used Git for my WordPress deployment workflow with both Pagodabox and Bedrock on EC2. Feels like I’m missing something here with the new release, is there a change in workflow? Normally I would just run grunt dev and just deploy like usual.

[image] KevinLisota: I assume the solution is to just remove the relevant lines in gitignore so that these can be versioned. I understand the desirability of not having to commit these generated assets, but for those of us using a Git deployment mechanism, I don’t see any other way to make this …

I have been relentlessly practicing this new Git deploy workflow to demonstrate it at my upcoming talk at WordCamp LAX . This is what I have and please let me know if I am making any errors or being redundant. I am primarily a designer and front-end developer, so I am learning as I go along with a lo…

As I am looking at this, I am seeing that there may be some unnecessary steps with grunt in my workflow. Particularly Step 1 and Step 2 in Part III. How can I add the tasks executed by grunt build into grunt watch? This way, I do not have to adjust wp-config.php and can simply deploy after saving c…

Getting Started
Releases
Support us

WP Packages is our new WPackagist replacement that's 17x faster and updates every 5 minutes

Roots Discourse

Using Roots 7.0 with Git deploy

sage

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled