Best Practices to update Custom Plugins

  • We have built a few custom plugins to run our e-com business on WordPress/woocommerce, so far so good. We still continue to innovate and release new versions of the custom plugins (all for internal purposes only). How do we handle this update process smoothly?

    Right now, I delete the old version of the custom plugin and upload the new plugin. This shuts the server off for at least 15-30mins, leave alone the surprises which might come later.

    What is a better way to handle this process? I like the way the open/published WordPress plugins handle the same. It is so seamless.

    Can someone point me how to handle our custom plugin update process?

    Thanks in Advance. Cheers, Y

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    You can update the ‘normal’ way via github with https://github.com/afragen/git-updater

    I have a site where I use a plugin (civicrm) that cannot be updated from the repo. Via SSH, I go to /tmp on the server and download the zip file for the plugin then use something like this:

    cd /path/to/plugins; sudo mv civicrm /tmp; sudo unzip /tmp/civicrm-version.zip; sudo chown -R correct-user:correct-user civicrm

    That takes only the time necessary to unzip plus maybe another second.

    This is also what I suggest you look at.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Best Practices to update Custom Plugins’ is closed to new replies.