It could be done across separate systems and perhaps will be in time, but PushLive in simplicity was originally designed for one purpose – to have a fully functioning staging site for updating and editing until you’re happy with the changes/results and ready to make them live. Replication (coming soon) will initially be for local systems only – and its main purpose will simply be to create an initial clone of a current site to begin the staging process with.
Ok, thanks for explanation.
Cheers,Tom
No problem Tom, thank you for your input – the more input the better PushLive can be tailored to the needs of it’s users. I imagine that once we get local replication working (easy to do, just takes time to code and test), it will be pretty easy to add remote replication as well.
Thanks again!
Jamin
Jamin
Is there any timeline on the replication feature? Your plugin is the closest to what I’m trying to build on a site with the exception of system replication. I’d like to have a system inside my firewall that is used for content submission, page editing, plugin and theme testing, etc., that then gets pushed to a load balanced public site via SSH/SFTP using certificates so that there is no editing or logging into the public site. My users are not technical so I like the simplicity of publish/review/push.
The replication feature is coming soon – I can’t give a specific timeline as it’s based on when we have free time to work on it.
However if you want to allow your users to access your site administration without having to use a username or password to login and you know they will be working behind static (unchanging) ip’s – one of these plugins should help with that – https://wordpress.org/plugins/search.php?type=term&q=ip+auto+login
Some allow you to create a WordPress user that’s connected to specific IP’s so that when someone from that IP accesses your staging site they will automatically be logged in without a password prompt.
In the PushLive setup you’ll simply want to uncheck the table for the IP based plugin that stores the allowed IP’s so that the users are not able to edit the live site as well. Also, making sure certain users are not enabled on the live site while following the suggested PushLive setup suggestions (they’re located right on the PushLive setup page) will prevent certain users from accessing the live site.
Hope this helps. Let us know if you have any issues.
You should also be able to further firewall access to your staging site for added security using various linux based tools.
