Server GTM Hosting has moved to its own platform.

Visit TagLinc(opens in a new tab)

The Professional WordPress Workflow: Local, Git, Staging, Live

How an agency or developer team can build, test and ship WordPress changes safely on FlyNode.

2 min readUpdated Oct 19, 2026FlyNode docs
Browse documentation

Need a hand?

Can't find your answer? Our team replies fast.

Contact support

This is the way many agencies work, and FlyNode has the pieces for it. Code travels in Git. Content and settings travel with Push to Production. Every step to the live site has a backup or an automatic way back.

The steps

  1. Build locally. Keep the whole site in one private repository and work on your own computer with Local. The setup is in Git Sync for Your WordPress Website.
  2. Push to the staging branch (staging) and press Pull from Git and Deploy Staging on the staging copy of the site, or let a webhook do it.
  3. Check it on staging. Staging is a full copy of the live site with its own database, so you can test with real content. Create it on the Staging tab (see Staging and Push to Production).
  4. Merge to the live branch (for example main) and press Pull from Git and Deploy Live. Turn on the webhook with live deploys if your team wants a merge to go live by itself.
  5. FlyNode protects the live site. It puts the site into maintenance mode for a moment, replaces the files, checks the site, and puts the old files back if the check fails.
  6. Undo if you need to. Previous version brings back what was there before the last deploy.

Which tool for which change

What changedUse
Code: your themes, plugins, templates, files of the siteGit sync (this workflow)
Live settings such as debug on, extra constantsfn-config.php in the repository
Posts, pages, settings, WooCommerce data, third-party pluginsPush to Production from staging
Updates to WordPress, plugins and themes from wordpress.orgUpdates with backup and rollback

Tips

  • Keep the repository private. Protect your live branch in your Git host so only reviewed changes reach it.
  • Keep secrets out of the repository: wp-config.php stays out of Git on your side and is never replaced on the site by a deploy.
  • Before a big release, run Push to Production or a backup first so the database has a restore point as well.

Still stuck?

Open a support ticket from your dashboard and include the container name.

Contact support