Build and Deployment Page in Wiki

[ninjasort]

Would it be possible to add some documentation for the build process and a basic deployment strategy?

[wesleytodd]

Sorry for the long delayed response, busy with work and the holidays. Anyway, I would love to have some documentation on a build and deployment process. The only issue I have right now is that YeoPress does not really have a prescribed deployment process. The way I personally handle this is something like this:

• Run yo wordpress, use Git and Wordpress as a submodule
• Develop theme, push site to github/bitbucket
• On production server, setup database
• Export local database and import on prod server
• Clone repo to production server, git submodule init && git submodule update
• Make updates and edits after launch, push to remote repo
• Pull on prod server

Does that sound like what you mean for a deployment strategy? If you are interested in putting together some good documentation I would love the contribution. I believe you can just edit the wiki if you want. Maybe make a page called Deployment. We could even try to document a few different deployment strategies.

[ninjasort]

Okay, reasonable.

What about some way to build from a Grunt task that would push the minified/optimized project to a staging branch? After it's been tested once more with optimizations, it could merge to a master/production branch.

Here's what I'm referencing: http://nvie.com/posts/a-successful-git-branching-model/

[wesleytodd]

Ahh, I see what you mean. I was thinking more about the basics of deployment. I am not sure YeoPress should be dictating git workflow. Maybe you could look at using https://github.com/nvie/gitflow with grunt? There might be some plugins out there. If you do want to do that, then I would be happy to add support to the gruntfile. But other than that I am not sure what YeoPress can provide in this respect.

[ninjasort]

Thanks for the tips.