New to the community? Start here

Workflow – Staging – Shipper

Hi!

I’m a novice and currently setting up my workflow. I am using WPMUDEV hosting and now have a live site and also a staging site. In addition I have also setup a local dev site which sits on DesktopServer.

From a workflow perspective I was thinking that I could do my development on the local version of the site then use Shipper to move the site to the staging site then when happy use the WPMUDEV hosting tool to push the staging site up to the production site.

My first question is do you think this is a logical workflow, if not what tends to be best practice?

Assuming the above is logical I then attempt to use the Shipper plugin to import to the staging site from the local site. Within Shipper I then have the issue that the “Requirements failed”, due to password protection being in place on the staging site. Looking at the documentation it seems that it is not possible to temporarily turn off the password protection. How do I get around this?

Many Thanks,
Dave

Wed, 6 Nov 2019 11:01:20
More Shipper Pro discussions
Shipper Pro
  • Dimitris Kalliris
    • Support Team Lead

    Hello there Dave

    I’m afraid that you can’t surpass this limitation as HTTP authentication can’t be disabled in the staging environment. Keep in mind that in order for Shipper to work, both sites (source and destination) should be publicly available and added to the Hub.

    May I ask why you prefer working locally and not directly to the staging site?
    Is there any other limitation or missing functionality that prevents you from doing so?
    Please advise!

    Thank you,
    Dimitris

  • Dave
    • Flash Drive

    Hi Dimitris, and thanks for coming back.

    I thought that might be the answer re Shipper.

    Re working locally I’m still trying to get to grips with the best working practices as I’m starting out. I’m guessing the reason some people do this is for speed of a local site? My sites are very basic at this stage so I think your suggestion is best, i.e. develop on the staging site then push to the live site.

    I was also wondering if I should be learning GIT to work locally and then push to live, but I suspect I should worry about that a bit further down the line.

    Thaks for your help,
    Dave

  • Dimitris Kalliris
    • Support Team Lead

    Building directly in a staging site shouldn’t be that slow, especially as there won’t be any other traffic from other users that create additional load on the server.

    Git would be a great choice as it’s already enabled in our hosting and you will also preserve a nice “log” of site changes. :wink:

    Warm regards,
    Dimitris