Git-Push-Deploy Add-on for PaaS
The Git-Push-Deploy add-on creates a simple CI/CD pipeline for any application on MassiveGRID PaaS: connect a Git repository and branch, and every push triggers an automatic pull and redeploy to the application servers, with optional build commands and post-deploy hooks. No CI server required.
Both buttons open the MassiveGRID PaaS dashboard with Git-Push-Deploy pre-selected. The trial needs no credit card.
Git-Push-Deploy Package Facts
| Attribute | Value |
|---|---|
| Package | Git-Push-Deploy Add-On |
| Type | Add-on (attaches to an existing environment) |
| Category | Add-ons & Utilities |
| Software vendor / project | Jelastic / Virtuozzo (package) |
| Licence | Open-source add-on |
| Runtime / stack | Add-on for application server layers (PHP, Node.js, Python, Ruby, Go, Java); webhook-driven deployment from GitHub, GitLab, Bitbucket or any Git host |
| Regions | New York, London, Frankfurt, Singapore |
| Billing | Free add-on; the host environment is billed per use from $2.46/month |
| Free trial | 14 days, no credit card |
| Uptime SLA | 100% |
What is Git-Push-Deploy?
Most projects do not need a full CI platform to get code onto a server. They need a reliable, repeatable way to make the current branch live. This add-on registers a webhook with your Git host (GitHub, GitLab, Bitbucket or any server that can call a URL) and, when a push arrives, fetches the code, runs the commands you configure (Composer, npm install, migrations, cache clears) and deploys to every node in the layer in turn.
It works with PHP, Node.js, Python, Ruby, Go and Java application servers, including those created by marketplace packages such as Laravel and Django CMS. Deployments are logged, and a failed build leaves the previous version running.
What Git-Push-Deploy Changes in Your Environment
Add-ons run against an environment you already have. Nothing is rebuilt, and the change can be removed from the same dashboard.
- Repository connection: Repository URL, branch and credentials or deploy key configured in the add-on.
- Webhook endpoint: A URL you add to the Git host so pushes notify the platform instantly (or use periodic polling).
- Deploy pipeline: Pull, optional build commands, deployment to each node with a graceful reload, and post-deploy hooks.
- Deployment log: Output of each run available in the dashboard for troubleshooting.
Why Teams Choose Git-Push-Deploy
Push is the release
Merge to the deploy branch and the change is live in a minute or two.
Any Git host
GitHub, GitLab.com, Bitbucket, a self-hosted GitLab or Gitblit, or any server that can send a webhook.
Build steps included
Run dependency installs, asset builds and migrations as part of the deploy.
Multi-node aware
Deploys to every application server in the layer, including nodes added by scaling.
How to Add Git-Push-Deploy on MassiveGRID PaaS
Attaching the add-on takes three steps and a few minutes of waiting. No servers to provision, no configuration files to edit.
Open the installer
Click Install with free trial or Install to my account. The MassiveGRID PaaS dashboard opens with the Git-Push-Deploy add-on pre-selected, so nothing has to be copied or pasted.
Sign up or sign in
New to the platform? Sign up for the free 14-day trial, which needs no credit card. Existing customers sign in with their usual dashboard credentials.
Pick the target environment
Choose the environment, and where relevant the node layer, that Git-Push-Deploy should attach to, then confirm. The add-on configures itself on the running nodes without a redeploy.
Who Runs Git-Push-Deploy on PaaS
Web application teams
Laravel, Django, Node.js and Rails projects that want automated deployments without Jenkins.
Agencies
Per-client environments each tracking a branch of the client's repository.
Staging environments
A staging server that always reflects the develop branch.
Why Run Git-Push-Deploy on MassiveGRID PaaS
Built for uptime. Git-Push-Deploy runs on MassiveGRID's high-availability platform, where every environment is covered by a 100% uptime SLA. Nodes live on redundant hosts, storage is replicated, and failed containers are restarted or migrated automatically.
Pay for what you use. Billing is hourly and per cloudlet (128 MiB RAM plus 400 MHz CPU). Vertical auto-scaling adds and removes cloudlets as load changes, so a quiet Git-Push-Deploy environment costs a few dollars a month and a busy one grows without a migration. Full details are on the PaaS page.
Your choice of jurisdiction. Deploy in New York, London, Frankfurt or Singapore and keep data inside the region your users or regulators require. MassiveGRID is ISO 9001 certified and GDPR compliant, and has run hosting infrastructure since 2003.
No lock-in. The package is a standard Jelastic Packaging Standard (JPS) manifest. You keep root-level access to the containers, can export the manifest, and can move the workload to any other Jelastic-compatible platform or to your own servers at any time.
Related on massivegrid.com: For Developers · DevOps Support.
Git-Push-Deploy Questions
More from the Marketplace
Packages that are often deployed alongside Git-Push-Deploy, or that solve the same problem a different way. Browse all 84 packages.
Deploy Git-Push-Deploy Today
Start the free 14-day trial and have Git-Push-Deploy running in minutes. No credit card required.