GitHub Webhooks - Revision history

KazVee: KazVee moved page Webhooks to GitHub Webhooks without leaving a redirect

2025-06-01T18:31:19Z

KazVee moved page Webhooks to GitHub Webhooks without leaving a redirect

← Older revision	Revision as of 18:31, 1 June 2025
(No difference)

KazVee: Add header

2025-06-01T18:11:53Z

Add header

← Older revision		Revision as of 18:11, 1 June 2025
Line 1:		Line 1:
			== Update Your Website with GitHub Webhooks and Plesk ==

	If you keep your website files in GitHub, you can set up automatic deployment using GitHub webhooks and Plesk. This means every time you push changes to your GitHub repository, your site will update automatically, with no need to manually upload files via FTP or the Plesk file manager.		If you keep your website files in GitHub, you can set up automatic deployment using GitHub webhooks and Plesk. This means every time you push changes to your GitHub repository, your site will update automatically, with no need to manually upload files via FTP or the Plesk file manager.

KazVee: Add punctuation for consistency

2025-06-01T18:07:36Z

Add punctuation for consistency

KazVee: Fix the step numbers for both major sections

2025-06-01T17:59:53Z

Fix the step numbers for both major sections

← Older revision		Revision as of 17:59, 1 June 2025
Line 19:		Line 19:
	6) Click on the blue '''Create''' button.		6) Click on the blue '''Create''' button.

	You should see a success message of '''Deploying files to domain.helioho.st''' and a link to '''Open the Git repository'''.		7) You should see a success message of '''Deploying files to domain.helioho.st''' and a link to '''Open the Git repository'''.

	7) You should be able to visit your deployed site on HelioHost.		8) You should be able to visit your deployed site on HelioHost.

	== Setup GitHub Webhooks ==		== Setup GitHub Webhooks ==
Line 27:		Line 27:
	To enable Plesk to get notifications of changes you make to files in your GitHub repo, so it can automatically deploy the updates to HelioHost for you, use the webhooks feature.		To enable Plesk to get notifications of changes you make to files in your GitHub repo, so it can automatically deploy the updates to HelioHost for you, use the webhooks feature.

	8) Inside Plesk, go back to the Git section, and click on the '''Repository settings''' button		1) Inside Plesk, go back to the Git section, and click on the '''Repository settings''' button

	[[File:repo_settings_2.png]]		[[File:repo_settings_2.png]]

	9) Copy the '''Webhook URL'''		2) Copy the '''Webhook URL'''

	10) Go to your GitHub repo, and go to '''Settings > Webhooks'''		3) Go to your GitHub repo, and go to '''Settings > Webhooks'''

	[[File:github_webhooks_3.png]]		[[File:github_webhooks_3.png]]

	11) Click on the '''Add webhook''' button.		4) Click on the '''Add webhook''' button.

	12) Paste the '''Webhook URL''' you copied from Plesk into the '''Payload URL''' field in GitHub.		5) Paste the '''Webhook URL''' you copied from Plesk into the '''Payload URL''' field in GitHub.

	13) Click on the '''Add webhook''' button		6) Click on the '''Add webhook''' button

	[[File:Webhook_url_4.png]]		[[File:Webhook_url_4.png]]

	14) You should see a success message of '''Okay, that hook was successfully created. We sent a ping payload to test it out!'''		7) You should see a success message of '''Okay, that hook was successfully created. We sent a ping payload to test it out!'''

	15) Update your site files, then commit and push the code changes to your GitHub repo.		8) Update your site files, then commit and push the code changes to your GitHub repo.

	16) The code changes will be deployed by Plesk, and your HelioHost website will reflect the latest changes.		9) The code changes will be deployed by Plesk, and your HelioHost website will reflect the latest changes.

	== Troubleshooting ==		== Troubleshooting ==

KazVee: Add new 'Update Your Website with GitHub Webhooks and Plesk' tutorial

2025-06-01T17:56:20Z

Add new 'Update Your Website with GitHub Webhooks and Plesk' tutorial

New page

If you keep your website files in GitHub, you can set up automatic deployment using GitHub webhooks and Plesk. This means every time you push changes to your GitHub repository, your site will update automatically, with no need to manually upload files via FTP or the Plesk file manager.

== Add GitHub Repo to Plesk ==

1) To to GitHub, and copy the link to clone your repository.

2) Login to your HelioHost account and navigate to:

'''Plesk > Websites & Domains > [ domain ] > Dashboard > Dev Tools > click on the Git button'''

[[File:git_button_1.png]]

3) Click on the blue '''Add Repository''' button

4) In the '''Repository URL''' field, paste in the web URL provided to you by GitHub

5) If you want files deployed to the webroot folder, leave the '''Server path''' set to '''/httpdocs'''. If you prefer to deploy files to a directory, enter it as '''/httpdocs/foldername'''.

6) Click on the blue '''Create''' button.

You should see a success message of '''Deploying files to domain.helioho.st''' and a link to '''Open the Git repository'''.

7) You should be able to visit your deployed site on HelioHost.

== Setup GitHub Webhooks ==

To enable Plesk to get notifications of changes you make to files in your GitHub repo, so it can automatically deploy the updates to HelioHost for you, use the webhooks feature.

8) Inside Plesk, go back to the Git section, and click on the '''Repository settings''' button

[[File:repo_settings_2.png]]

9) Copy the '''Webhook URL'''

10) Go to your GitHub repo, and go to '''Settings > Webhooks'''

[[File:github_webhooks_3.png]]

11) Click on the '''Add webhook''' button.

12) Paste the '''Webhook URL''' you copied from Plesk into the '''Payload URL''' field in GitHub.

13) Click on the '''Add webhook''' button

[[File:Webhook_url_4.png]]

14) You should see a success message of '''Okay, that hook was successfully created. We sent a ping payload to test it out!'''

15) Update your site files, then commit and push the code changes to your GitHub repo.

16) The code changes will be deployed by Plesk, and your HelioHost website will reflect the latest changes.

== Troubleshooting ==

=== Fatal: You are on a branch yet to be born ===

If you get an error message of '''fatal: You are on a branch yet to be born'''

Make sure your GitHub repo is not empty.

=== Destination path already exists and is not an empty directory ===

If you get an error of '''fatal: destination path '/home/domain.helioho.st/git/repo_name.git' already exists and is not an empty directory.'''

Try deleting the existing repo folder inside '''Plesk > Home directory > git > repo_name''' and try to add the Repository URL again.

=== Fatal: could not read Username for github.com: No such device or address ===

If you get an error of '''Cloning into bare repository /home/domain.heliohost.us/git/repo_name.git fatal: could not read Username for github.com: No such device or address'''

Make sure you provided the correct GitHub repo URL.

== References ==

This tutorial is adapted from user-provided information in the [https://helionet.org/index/topic/64197-adding-git-submodules/#findComment-290016 Adding Git Submodules] post on the [https://helionet.org/index/ HelioNet forum].

== Further Support ==

If this tutorial has not worked for you, please go back and check all of your steps again to make sure you didn't miss anything. If you can't figure out what is wrong, please post in the [https://helionet.org/index/forum/45-customer-service/?do=add Customer Service forum], making sure to provide your '''username''' and any '''error message(s)''' received.

[[Category:Tutorials]]

← Older revision		Revision as of 18:07, 1 June 2025
Line 11:		Line 11:
	[[File:git_button_1.png]]		[[File:git_button_1.png]]

	3) Click on the blue '''Add Repository''' button		3) Click on the blue '''Add Repository''' button.

	4) In the '''Repository URL''' field, paste in the web URL provided to you by GitHub		4) In the '''Repository URL''' field, paste in the web URL provided to you by GitHub.

	5) If you want files deployed to the webroot folder, leave the '''Server path''' set to '''/httpdocs'''. If you prefer to deploy files to a directory, enter it as '''/httpdocs/foldername'''.		5) If you want files deployed to the webroot folder, leave the '''Server path''' set to '''/httpdocs'''. If you prefer to deploy files to a directory, enter it as '''/httpdocs/foldername'''

	6) Click on the blue '''Create''' button.		6) Click on the blue '''Create''' button.

	7) You should see a success message of '''Deploying files to domain.helioho.st''' and a link to '''Open the Git repository'''.		7) You should see a success message of '''Deploying files to domain.helioho.st''' and a link to '''Open the Git repository'''

	8) You should be able to visit your deployed site on HelioHost.		8) You should be able to visit your deployed site on HelioHost.
Line 27:		Line 27:
	To enable Plesk to get notifications of changes you make to files in your GitHub repo, so it can automatically deploy the updates to HelioHost for you, use the webhooks feature.		To enable Plesk to get notifications of changes you make to files in your GitHub repo, so it can automatically deploy the updates to HelioHost for you, use the webhooks feature.

	1) Inside Plesk, go back to the Git section, and click on the '''Repository settings''' button		1) Inside Plesk, go back to the Git section, and click on the '''Repository settings''' button.

	[[File:repo_settings_2.png]]		[[File:repo_settings_2.png]]
Line 41:		Line 41:
	5) Paste the '''Webhook URL''' you copied from Plesk into the '''Payload URL''' field in GitHub.		5) Paste the '''Webhook URL''' you copied from Plesk into the '''Payload URL''' field in GitHub.

	6) Click on the '''Add webhook''' button		6) Click on the '''Add webhook''' button.

	[[File:Webhook_url_4.png]]		[[File:Webhook_url_4.png]]
Line 61:		Line 61:
	=== Destination path already exists and is not an empty directory ===		=== Destination path already exists and is not an empty directory ===

	If you get an error of '''fatal: destination path '/home/domain.helioho.st/git/repo_name.git' already exists and is not an empty directory.'''		If you get an error of '''fatal: destination path '/home/domain.helioho.st/git/repo_name.git' already exists and is not an empty directory'''

	~~Try deleting~~ the existing repo folder inside '''Plesk > Home directory > git > repo_name''' and ~~try to~~ add the Repository URL again.		Delete the existing repo folder inside '''Plesk > Home directory > git > repo_name''' and add the Repository URL again.

	=== Fatal: could not read Username for github.com: No such device or address ===		=== Fatal: could not read Username for github.com: No such device or address ===