README and instructions

[rememberlenny]

I've been researching how to implement Capistrano into my wordpress workflow and feel like there is a lot of potential in the WP-stack script templates. Currently its very unclear what files you need to modify and what the effect of modifications are. I would like to write some concrete explanation of what your server/local system structure should be and a step-by-step guide as to how to get WP-Stack up and running.

Apart from the public README, is there any existing documentation I can work off of?

I talked with Robbie for a bit yesterday and I understood a bit of how Knewton structures their servers. Its very helpful to understand the structure in which WP-Stack is most useful. I've attached the flowchart I made.

Structure

Servers

It is meant to be read from left to right. On the left is your own machine. The "Local" is a virtual server running off Vagrant. The "Repo" is working on Github. The "Admin Box" is the remote controller for managing the "Staging" and "Production" servers.

Databases

The Databases themselves are backedup on Vaultpress. Whenever there is local work done, the database is pulled from the remote servers. When changes need to be made to the databases, the processes made locally and replayed on the remote servers.

[getdave]

Thank you for this. I agree the "flow" needs to be improved.

So in order to configure WP Stack do you have to have you "local" as a virtual server? Currently my development is run from my MacBook. Is it possible to configure deployments in a manner that would work with this setup?

[rememberlenny]

@getdave A virtual server can be anything from a Vagrant Box (virtualized linux) or a MAMP/XAMPP installation.

[mattstratton]

The thing that is really unclear to me is where WP-Stack should exist. I know that the capistrano type files should live inside the directory of the site, but should wp-stack be created as a submodule?

[phillcoxon]

I would be very happy to help with documenting this process as it is very confusing at the moment for people starting out.

I've got Vagrant running locally for testing and I'm extremely impressed.

Has Robbie's Vagrant configuration script been made available? Or has anyone else published a Vagrant config for a similar setup that can be used as a base to document a step-by-step setup?

Also, in Robbie's example the 'vagrant knewton:sync' and 'vagrant knewton:localdev on' - is the database syncing & localhost modification functionality part of Vagrant as standard or part of Robbie's custom Vagrant config?

Is anyone available to spend a little bit of time helping me document this process to make it far easier for new people (including myself) to get started?

Thanks!

[rememberlenny]

Id appreciate having a reference Vagrant script. I don't think one has.

Leonard Bogdonoff
Lkbgift@gmail.com (mailto:Lkbgift@gmail.com)
Blog (http://lkb.cc) | Github (http://github.com/lkbgift) | Portfolio (http://rememberlenny.com)
@Lkbcc (http://twitter.com/lkbcc) | 949-322-8496 (tel:1-949-322-8496)

On Friday, April 26, 2013 at 9:01 PM, getresults wrote:

I would be very happy to help with documenting this process as it is very confusing at the moment for people starting out.
I've got Vagrant running locally for testing and I'm extremely impressed.
Has Robbie's Vagrant configuration script been made available? Or has anyone else published a Vagrant config for a similar setup that can be used as a base to document a step-by-step setup?
Also, in Robbie's example the 'vagrant knewton:sync' and 'vagrant knewton:localdev on' - is the database syncing & localhost modification functionality part of Vagrant as standard or part of Robbie's custom Vagrant config?
Is anyone available to spend a little bit of time helping me document this process to make it far easier for new people (including myself) to get started?
Thanks!

—
Reply to this email directly or view it on GitHub (#13 (comment)).

[jfrux]

+1 I'm also very interested in a completely documented 'no-assumptions' README or Setup guide.
I'm familiar with Ruby/Rails and Capistrano but having the WP-Stack repo on the server makes very little sense to me...
I work locally, trying to get away from editing wordpress sites in production obviously, so this is what I've found. This repo looks promising but I'm not seeing enough clarification in the setup to really move on it.

The WordPress-Skeleton repo looks pretty clean cut...
I suspect the WP-Stack project might be better suited for a "methodology" or a guided policy versus an actual code-base.

I'm interested to see where this repo goes though for sure.