Wordpress strategy

[gerhard]

Wordpress strategy

[jessor]

yes!

[gerhard]

OK, so would you be putting the entire WP site directory under git or just specific dirs?

In my case, I prefer to have something like Chef or Puppet maintain the core CMS installation (be in WP or something else), my repo only containing the site's files. I'm thinking along the lines of a more generic deliver strategy (static sounds nice) where deliver doesn't care what it's pushing out. It can be just html stuff, or php (which doesn't normall require a web server restart).

Tell me what would make most sense for you and then I can work that in.

[videoMonkey]

Is this dead? I would like a static/php delivery, I'm about to start on it myself.

[gerhard]

If you put the whole Wordpress site under git, it works out of the box with the shared strategy. It's the most straightforward thing that you can do and it will just work:

Demi ➜  wordpress git:(master) HOSTS=apps.vagrant STRATEGY=shared deliver -V

BRANCH will be deprecated as of v0.8.0
SERVERS will be deprecated as of v0.8.0

DELIVERING WORDPRESS WITH SHARED STRATEGY

-----> Authorizing hosts
-----> Ensuring hosts are ready to accept git pushes
Initialized empty Git repository in /home/wordpress/app/.git/
-----> Pushing new commits with git to: [email protected]
Counting objects: 1124, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (1094/1094), done.
Writing objects: 100% (1124/1124), 4.95 MiB | 9.15 MiB/s, done.
Total 1124 (delta 70), reused 0 (delta 0)
To [email protected]:~wordpress/app
 * [new branch]      master -> master
-----> Resetting remote hosts to f7d61810c1af73eaaad26a753aadfd258b3ab8ea
HEAD is now at f7d6181 Initial commit
-----> Updating git submodules
-----> Setting file permissions

WORDPRESS DELIVERED!

[videoMonkey]

I hadn't dug into your updates and code enough, I just quickly glanced through the issues list and caught the keyword 'wordpress' which is exactly what I am looking to do. I am right now working out setting this up. On a note so related note, can this system revert a delivery to a previous version or do I need to look to another system?

[gerhard]

You revert a delivery by pushing an explicit version. The REFSPEC can be any valid git reference, tag, branch or commit.

[gerhard]

This has been implemented via the shared strategy

[videoMonkey]

awesome! this tool is working out to be everything I need, great work team!

[gerhard]

👍