Basic vs advanced mode might simplify things

[isarmstrong]

Hey Mark,

I've been trying your plugin in a few different environments lately and I got to thinking - why not support a basic vs advanced setup? You've got the hard one down already and it's really ideal for major sites.

For a personal blog though, you could probably just replicate the DB to a different prefix, copy the files to a dev folder, and call it a day. For the average (non-technical) WordPress customer, this would make a lot of sense since it would be damn near a one-click setup.

You've already done the hard part by setting up the plugin for advanced users. , Adding a less secure/bulletproof "basic" setup for the masses would probably be very well received.

[rowatt]

Hi Ian - thanks for your message. It's an interesting thought but I'm not sure it could be so close to a one-click setup. Even if SitePush just copied files to a 'dev' folder, you'd still need to hack the main index.php file, wp-config and probably .htaccess too. By the time someone's done that, I'm not sure it's going to be that much easier than currently.

Also, if by replicating the DB to a different prefix you mean use a different prefix for DB tables but keep the same DB, that's not so straightforward code wise because WP uses the DB prefix in some fields inside the DB. Possible, but a lot more things to check.

I can't see me working on a 'basic' mode any time soon. In the meantime, though, better documentation always helps, so let me know if you have any suggestions on that front.

[isarmstrong]

What I wouldn't give for a look at the code wpengine.com is using though ;)

My most recent issue was that I had to use a separate DB password -
something with symbols made the DB config non-parsable. Once it was up &
running the WP Admin menu for the push never showed up. It was odd. I'm
going to try swapping to the 2011 theme on that particular site and see if
it gets a better response. More on that in another thread when I'm done
testing the issues.

On Thu, Feb 21, 2013 at 6:21 PM, Mark Rowatt Anderson <
notifications@github.com> wrote:

Hi Ian - thanks for your message. It's an interesting thought but I'm not
sure it could be so close to a one-click setup. Even if SitePush just
copied files to a 'dev' folder, you'd still need to hack the main index.php
file, wp-config and probably .htaccess too. By the time someone's done
that, I'm not sure it's going to be that much easier than currently.

Also, if by replicating the DB to a different prefix you mean use a
different prefix for DB tables but keep the same DB, that's not so
straightforward code wise because WP uses the DB prefix in some fields
inside the DB. Possible, but a lot more things to check.

I can't see me working on a 'basic' mode any time soon. In the meantime,
though, better documentation always helps, so let me know if you have any
suggestions on that front.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-13925230.

[rowatt]

Well, WPEngine is just copying the database and copying the files to a different vhost - pretty much what SitePush is doing though with rather less flexibility. The big difference with WPEngine, is that because they control the infrastructure, they know exactly what files need to go where and how the databases are set up.

It would be rather easier to do a 'basic' SitePush mode if I was doing it for a single host setup. If any hosts out there want to adopt SitePush that would open up a range of possibilities.

If you are having problems with characters in passwords making the config file unparseable, try enclosing in quotes - that has worked in some cases.