1. Home
  2. Staging & Deployment
  3. Does Pagely Offer One-Click Deployment…

Does Pagely Offer One-Click Deployment Options?

Yes, setting up Git is the primary method our customers use for their deployment process. This provides your developers with a reliable and universal foundation for creating a 1-click deployment plan.

Check out our technical KB support articles on the topic:

Mentioned in the first article, you’ll find a tutorial for how to: creating a remote repository, creating a post-receive hook, adding your remote repository locally and pushing to your production instance/server. This assumes one repository per each site however the post-receive script could be adjusted to perform specific actions based upon the branch name and deploy to different sites based on that.

In the second article, we’ll go into how our Git Integration tool works located inside the Apps tab of your Pagely Atomic dashboard and necessary steps and considerations when deploying updates to your WordPress website.

Staging instances can be added easily from your Pagely dashboard and will reside on your VPS. If you’d like a dedicated staging server, our VBURST plans are an excellent resource for parsing out your environments.


It’s ideal to have a sane, multi-environmental process for consistency and risk aversion for deploying broken or wonky code to your live production site. Additionally, you can connect the site using DeployBot, DeployHQ or another form of Git deployment.

Note: We enable virtually every conceivable workflow for staging and deployment but given the near infinite number of permutations for tools and processes, we don’t impose one particular workflow via our UI.

Was this article helpful?