Skip to content

Commit aebbfc6

Browse files
authoredJul 12, 2024
Update descriptions (#21)
* Update descriptions * readme.md update * readme.md update * description.md update
1 parent 1f12c34 commit aebbfc6

9 files changed

+15
-15
lines changed
 

‎README.md

+12-11
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,16 @@
1-
## Simple Automated CI/CD Pipeline for Git Projects
2-
3-
This Git-Push-Deploy solution enables automatic delivery of updates within your Git application sources directly to the cloud. The package can be applied as an add-on to **Java**, **PHP**, **Ruby**, **Node.js**, **Python** and **Go** projects, run on top of [the certified stack templates](https://docs.jelastic.com/software-stacks-versions#app-servers).
1+
# Simple Automated CI/CD Pipeline for Git Projects
42

3+
This Git-Push-Deploy solution enables automatic delivery of updates within your Git application sources directly to the cloud. The package can be applied as an add-on to **Java**, **PHP**, **Ruby**, **Node.js**, **Python** and **Go** projects, run on top of [the certified stack templates](https://www.virtuozzo.com/application-platform-docs/software-stacks-versions/).
54

65
![git-push-deploy-pipeline](images/git-push-deploy-pipeline.png)
76

87
The workflow depends on the programming language used in your project:
9-
- *for Java-based projects*, the package initiates creation of separate environment with a [Maven build node](https://docs.jelastic.com/maven-cloud-hosting-in-jelastic), which will be responsible for interaction with remote Git repository, triggering your application builds and their deployment to application server
108

9+
- *for Java-based projects*, the package initiates creation of separate environment with a [Maven build node](https://www.virtuozzo.com/application-platform-docs/java-vcs-deployment/), which will be responsible for interaction with remote Git repository, triggering your application builds and their deployment to application server
1110
- *for PHP/Ruby/Node.js/Python/Go apps*, the package sets up a pipeline for project deployment directly to the ROOT context on a web server (consider that Ruby app servers are displayed with a deployment mode instead of a context within dashboard, though the actual project location is the same)
1211

12+
All related deployment operations are performed via [Application Platfom API](https://www.virtuozzo.com/application-platform-api-docs/). If a server runs multiple containers, all of them will be restarted sequentially (with a 30-second delay by default) during the update to eliminate possible application downtime. Beside that, a special [ZDT Deployment](https://www.virtuozzo.com/application-platform-docs/php-zero-downtime-deploy/) option is used for PHP applications, ensuring their constant availability even with a single application server node.
1313

14-
All related deployment operations are performed via [Jelastic API](https://docs.jelastic.com/api/). Herewith, if a server runs multiple containers, all of them will be restarted [sequentially](https://docs.jelastic.com/release-notes-49#sequential-restart-deploy) (with a 30-second delay by default) during the update to eliminate possible application downtime. Beside that, a special [ZDT Deployment](https://docs.jelastic.com/php-zero-downtime-deploy) option is used for PHP applications, ensuring their constant availability even with a single application server node.
1514

1615
## Requirements
1716

@@ -35,22 +34,24 @@ Before applying the package, please consider the following points:
3534
</project>
3635
```
3736

38-
[![Deploy](https://raw.githubusercontent.com/jelastic-jps/git-push-deploy/master/images/deploy-to-jelastic.png)](https://jelastic.com/install-application/?manifest=https://raw.githubusercontent.com/jelastic-jps/java-memory-agent/master/manifest.jps)
37+
[![Deploy to Cloud](images/deploy-to-cloud.png)](https://www.virtuozzo.com/install/?manifest=https://raw.githubusercontent.com/jelastic-jps/git-push-deploy/master/manifest.jps)
38+
3939

40-
## How to Integrate Git-Push-Deploy Pipeline to Jelastic Environment
40+
## How to Integrate Git-Push-Deploy Pipeline to PaaS Environment
4141

42-
To install the Git-Push-Deploy package, copy link to the **_manifest.jps_** file above and [import](https://docs.jelastic.com/environment-import) it to your Jelastic dashboard.
42+
To install the Git-Push-Deploy package, copy link to the **_manifest.jps_** file above and [import](https://www.virtuozzo.com/application-platform-docs/environment-import/) it to your application platform dashboard.
4343

44-
![git-push-deploy-installation](images/git-push-deploy-installation.png)
44+
![install git-push-deploy](images/install-git-push-deploy.png)
4545

4646
Within the opened installation window, specify the following data:
47+
4748
- **_Git Repo Url_** - HTTPS link to your application repo
4849
- **_Branch_** - a project branch to be used
4950
- **_User_** - your Git account login
5051
- **_Token_** - personal Git access token for webhook generation (can be created within [GitHub](https://github.com/jelastic-jps/git-push-deploy/wiki/GitHub-Access-Token)/[GitLab](https://github.com/jelastic-jps/git-push-deploy/wiki/GitLab-Access-Token) account settings)
5152
- **_Environment name_** - target environment your application should be deployed to
5253
- **_Nodes_** - application server name (is fetched automatically upon selecting the environment)
5354

54-
Click **Install** and wait for Jelastic to configure CI/CD pipeline for your project. Once your application is deployed, all the further changes, committed to a source repository, will be automatically delivered to your environment inside Jelastic Cloud.
55+
Click **Install** and wait for the platform to configure CI/CD pipeline for your project. Once your application is deployed, all the further changes, committed to a source repository, will be automatically delivered to your environment.
5556

56-
For more information on the package please refer to the article [Git Push Deploy to Containers](https://jelastic.com/blog/git-push-deploy-to-containers/).
57+
For more information on the package please refer to the article [Git-Push-Deploy to Containers](https://www.virtuozzo.com/application-platform-docs/git-push-deploy/).

‎images/deploy-to-cloud.png

2.64 KB
Loading

‎images/deploy-to-jelastic.png

-6.8 KB
Binary file not shown.
-65 KB
Binary file not shown.

‎images/how-get-private-keyid.png

-375 KB
Binary file not shown.

‎images/install-git-push-deploy.png

129 KB
Loading

‎manifest.jps

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@ type: update
22
version: 1.7
33
id: git-push-deploy
44
name: Git-Push-Deploy Add-On
5-
homepage: https://jelastic.com/blog/git-push-deploy-to-containers/
5+
homepage: https://www.virtuozzo.com/application-platform-docs/git-push-deploy/
66
baseUrl: https://raw.githubusercontent.com/jelastic-jps/git-push-deploy/master
77
description:
88
text: /text/description.md

‎text/description.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -4,5 +4,4 @@ In order to generate _Personal Access Token_ to your Git account, refer to the a
44
* [GitHub](https://github.com/jelastic-jps/git-push-deploy/wiki/GitHub-Access-Token/)
55
* [GitLab](https://github.com/jelastic-jps/git-push-deploy/wiki/GitLab-Access-Token/)
66

7-
This addon can be applied to any certified Java, PHP, Ruby, Python or Node.js application server.
8-
7+
This add-on can be applied to any certified Java, PHP, Ruby, Python, Golang, or Node.js application server.

‎text/success.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22

33
Open your target environment URL **[${env.protocol}://${env.domain}](${env.protocol}://${env.domain}/)** to access your application.
44

5-
If something does not work as expected, please check the logs for more details or submit a question to [Jelastic community](https://stackoverflow.com/questions/tagged/jelastic).
5+
If something does not work as expected, please check the logs for more details or submit a question to [community](https://stackoverflow.com/questions/tagged/jelastic).

0 commit comments

Comments
 (0)
Please sign in to comment.