• Resolved evanevans333

    (@evanevans333)


    I have a WP site at ie: domain.com and a copy of it at dev.domain.com

    So my question is, how would I set up both copies, with Revisr, such that once the dev.domain.com (staging) is the way we like (stable and ready to push to live), that it updates the live site?

    Is it just a matter of installing Revisr on both, and in Bitbucket or Github merging the modifications to the STAGE/DEV branch into the PRODUCTION branch? And then everything autoupdates?

    I need some help, understanding, and setting up this kind of setup with your plugin. And if I may, I recommend such a tutorial be a blog post on your site. It’s kind of the “killer” setup.b ??

    Thanks in advance for your patience, and time, and help.

    https://www.ads-software.com/plugins/revisr/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Expanded Fronts

    (@expandedfronts)

    Hi,

    Sorry for the delay. Documentation in this area is being worked on and will be updated this week. I’ve added some quick steps below that should work for most setups.

    Before doing anything, make sure you have a backup of your site files and database. It is currently possible to mess up your data if you’re not careful or aware of what you’re doing.

    • Install Revisr on your dev site, creating a new repo if necessary
    • Configure the “Files/Directories to ignore” (usually add the wp-config.php, .htaccess, and other environment-dependant files here – this updates the “.gitignore” file for the repo)
    • Commit any pending/untracked files via “Revisr”->”Commits”->”New Commit”
    • Configure the remote repo in the “Revisr Remote Settings” section
    • Push to the remote from within Revisr
    • Manually upload the “.git” folder and the “.gitignore” from your dev site to production (this is only necessary once)
    • Install Revisr on production
    • Make a commit on dev and push it up to bitbucket/github, production should see this and you should be able to pull this onto production. You could then also make a commit on production and push it up to bitbucket/github, and pull it down on dev

    The above implementation would just be a basic files only, non-automatic deployment setup, but once you have that set up it is easier to configure some of the more advanced settings such as the autopush/autopull and database import/export settings.

    One of the key things to note is that for most smaller to medium sized setups, it’s easiest to keep it all on a single branch, that way you can just do pushes/pulls without worrying about merging.

    If you need any more help setting this up feel free to shoot an email to [email protected] with more details on your specific setup, and stay tuned for updates to the docs over the next few days.

    Let me know if you have any questions, thanks!

    Thread Starter evanevans333

    (@evanevans333)

    Hmm. That’s all very interesting, and perhaps a little more confusing. ??

    I think I need to hire you for a consultation to set me up.

    I’ve got the dev site, I’ve got the bitbucket account, I’ve got the production site, I’ve backed up both production and dev sites, I’ve created .gitignore files. I’m thinking of doing a branch called PRODUCTION
    and a branch called MASTER, and maybe even one called DEV, though I could probably be fine with just MASTER and PRODUCTION and use the MASTER for the DEV server just the same.

    Essentially, whenever PRODUCTION changes, the changes will go live on the production server. To change PRODUCTION one would merge from MASTER. MASTER would represent the stable permanent build and would be mirrored in the PRODUCTION.

    DEV would be for sandboxing and staging.

    I want to hire freelance coders to come in to the private bit bucket repository for the DEV side, and add their features or fix the bugs, then merge those and push them to MASTER and/or PRODUCTION when they are fit for production.

    Your plugin is great for also handling local WordPress install changes in addition to many other benefits of course. I do worry about the Production site and the Dev site slipping out of sync somehow. But that seems to be where putting the copy of the .git folder into the production site comes in???

    I am also worried about the databases trying to match up. I am worried that some tables from the DEV could overwrite tables in the PRODUCTION.

    Mostly, I’m a bit confused because I’m a bit new to Git and I’m trying to connect a DEV server, a Bit Bucket repo, a Production server, and Freelance coders, and I don’t have the wisdom to have the foresight to know that setting up X thing in X way will cause X disaster or lack of ability in the future. If you have a PayPal or if you can lend me your skype or email, if we can connect somehow, I’m happy to see if I can pay you for your help in setting me up. I have been struggling with this for a few days, and need someone who knows what they are doing to just connect it all up the right way. I could mess with it, until it appears to work but you would KNOW what to do to make it work.

    Thread Starter evanevans333

    (@evanevans333)

    I will also send you an email. I didn’t see you gave your email. Thanks

    Plugin Author Expanded Fronts

    (@expandedfronts)

    Hi, responded via email and marking this thread as resolved while we work on your setup externally.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Setting up Stage and Production’ is closed to new replies.