Skip to content

Commit 20b2b79

Browse files
authored
Merge pull request #110 from packagist/clarify-integration-setup
Integrations: update GitHub guides
2 parents 9f01b3b + bb9562b commit 20b2b79

27 files changed

+81
-31
lines changed
Binary file not shown.
Loading
Loading
Loading
Loading
Binary file not shown.
Binary file not shown.
Loading
Binary file not shown.
Binary file not shown.
Loading
Loading
Loading
Loading
Loading
Binary file not shown.
+35-11
Original file line numberDiff line numberDiff line change
@@ -1,31 +1,55 @@
1-
# GitHub (Enterprise) Integration Setup
1+
# GitHub Enterprise Integration Setup
22
## Private Packagist Cloud
33

4-
## Initial Setup
4+
<div class="row column">
5+
<div class="callout success">
6+
<p>
7+
This guide explains how to set up an OAuth integration for Private Packagist Cloud with GitHub Enterprise Cloud/Server.
8+
If you use their public service on GitHub.com, these instructions are not relevant to you.
9+
</p>
10+
<p>If you are using our Self-Hosted product, please <a href="/docs/self-hosted/github-integration-setup">use this guide</a>.</p>
11+
</div>
12+
</div>
13+
14+
To allow your users to authenticate to Private Packagist with their GitHub Enterprise account, you'll first need to create
15+
an integration in Private Packagist. This document walks you through the required steps.
16+
17+
## Open the Add Integration form
518

619
From the organization settings page, select the "Integrations" subtab. Hit the "Add Integration" button on the integrations listing page to get to the form below.
720
To set up a GitHub Enterprise integration with Private Packagist start by selecting "GitHub" as the platform and enter the URL of your GitHub Enterprise server, as seen in the example below.
8-
A link to setup the OAuth application on your GitHub enterprise server will automatically be displayed.
21+
A link to create a new OAuth application on your GitHub Enterprise server will automatically be displayed.
922

10-
![Packagist Setup](/Resources/public/img/docs/integration-setup/cloud/github-enterprise-01-packagist-setup.png)
23+
![Packagist Setup](/Resources/public/img/docs/integration-setup/cloud/github-enterprise-01-packagist-setup-20241219.png)
1124

12-
## Creating an OAuth Application
25+
## Create a GitHub Enterprise OAuth Application
1326

1427
Do not submit the integration form yet, but copy the content from the "Callback
1528
URL / Redirect URL" and follow the setup link to your GitHub server. The fields
1629
Client ID and Client Secret remain empty for now.
1730

18-
![GitHub Register App](/Resources/public/img/docs/integration-setup/github-02-github-register-app.png)
31+
![GitHub Register App](/Resources/public/img/docs/integration-setup/cloud/github-enterprise-02-register-app.png)
1932

20-
Register a new application on GitHub. This will reveal the client ID and client
21-
secret required for finishing the setup on Private Packagist.
33+
Register a new application on GitHub Enterprise. You'll be redirected to the application's page. Click the "Generate a new client secret" button
34+
to get a new secret. You'll need the client ID and client secret to finish the setup on Private Packagist.
2235

23-
![GitHub Credentials](/Resources/public/img/docs/integration-setup/github-03-github-credentials.png)
36+
![GitHub Credentials](/Resources/public/img/docs/integration-setup/github-03-github-credentials-20241219.png)
2437

25-
## Finish the Setup
38+
## Create the integration
2639

2740
Copy and paste the "Client ID" and "Client Secret" values back into the Private
2841
Packagist integration form and submit the form with the "Save Integration"
2942
button.
3043

31-
![Packagist Form](/Resources/public/img/docs/integration-setup/cloud/github-enterprise-04-packagist-form.png)
44+
![Complete integration form](/Resources/public/img/docs/integration-setup/cloud/github-enterprise-04-complete-form.png)
45+
46+
You'll be redirected back to the list of integrations.
47+
48+
### Share the GitHub Enterprise login link
49+
50+
The final step is sharing your organization-specific login link with your users. Look for the "Login link" button next to
51+
your newly created GitHub Enterprise integration on the integrations page, and copy the URL.
52+
53+
![GitHub Enterprise integration](/Resources/public/img/docs/integration-setup/cloud/github-enterprise-05-integration.png)
54+
55+
This link presents the option to authenticate with your GitHub Enterprise account and can now be used to log in to Private Packagist.

docs/self-hosted/bitbucket-integration-setup.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
## Initial Setup
1111
Hit the “Add Integration“ button on the admin page to get to the form below.
1212

13-
![Add Integration](/Resources/public/img/docs/self-hosted/08-integration.png)
13+
![Add Integration](/Resources/public/img/docs/self-hosted/08-integration-create.png)
1414

1515
To setup a Bitbucket integration with Private Packagist start by selecting "Bitbucket" as the platform and enter <i>https://bitbucket.org</i> as the base URL, as seen in the example below.
1616

+37-13
Original file line numberDiff line numberDiff line change
@@ -1,28 +1,52 @@
11
# GitHub (Enterprise) Integration Setup
22
## Private Packagist Self-Hosted
33

4-
This guide explains how to setup an OAuth integration for Private Packagist Self-Hosted with either the on-premises version of GitHub, or their public service on github.com.
5-
If you are using our cloud product at packagist.com, [use this guide](../cloud/github-integration-setup.md).
4+
<div class="row column">
5+
<div class="callout success">
6+
<p>This guide explains how to set up an OAuth integration for Private Packagist Self-Hosted with either the on-premises version of GitHub, or their public service on GitHub.com.</p>
7+
<p>If you are using our Cloud product at packagist.com, <a href="/docs/cloud/github-integration-setup">use this guide</a>.</p>
8+
</div>
9+
</div>
610

7-
## Initial Setup
8-
Hit the “Add Integration“ button on the admin page to get to the form below.
11+
To allow your users to authenticate to Private Packagist Self-Hosted with their GitHub or GitHub Enterprise account, you'll
12+
first need to create an integration in Private Packagist. This document walks you through the required steps.
913

10-
![Add Integration](/Resources/public/img/docs/self-hosted/08-integration.png)
14+
## Open the Add Integration form
1115

12-
To setup a GitHub integration with Private Packagist start by selecting "GitHub" as the platform and enter the URL of your GitHub Enterprise Server or <i>https://github.com</i> to use the public GitHub server as seen in the example below. A link to setup the OAuth application on GitHub will automatically be displayed.
16+
Go to the Admin section and hit the “Add Integration“ button to open the form to create your integration. If you've just
17+
installed Private Packagist Self-Hosted and it is still running in Setup Mode, you do not need to log in. If the application
18+
is no longer in Setup mode, you will have to log in with an admin account first.
1319

14-
![Packagist Setup](/Resources/public/img/docs/integration-setup/github-01-packagist-setup.png)
20+
![Add Integration](/Resources/public/img/docs/self-hosted/08-integration-create.png)
21+
22+
To setup a GitHub integration with Private Packagist start by selecting "GitHub" as the platform and enter the URL of
23+
your GitHub Enterprise Server or <i>https://github.com</i> to use the public GitHub server as seen in the example below.
24+
A link to set up the OAuth application on GitHub will automatically be displayed.
25+
26+
![Packagist Setup](/Resources/public/img/docs/integration-setup/self-hosted/github-01-packagist-setup.png)
1527

1628
## Creating an OAuth Application
17-
Do not submit the integration form yet, but copy the content from the "Callback URL / Redirect URL" and follow the setup link to your GitHub server. The fields Client ID and Client Secret remain empty for now.
29+
Do not submit the integration form yet, but copy the content from the "Callback
30+
URL / Redirect URL" and follow the setup link to your GitHub server. The fields
31+
Client ID and Client Secret remain empty for now.
1832

19-
![GitHub Register App](/Resources/public/img/docs/integration-setup/github-02-github-register-app.png)
33+
![GitHub Register App](/Resources/public/img/docs/integration-setup/self-hosted/github-02-github-register-app.png)
2034

21-
Register a new application on GitHub. This will reveal the client ID and client secret required for finishing the setup on Private Packagist.
35+
Register a new application on GitHub Enterprise. You'll be redirected to the application's page. Click the "Generate a new client secret" button
36+
to get a new secret. You'll need the client ID and client secret to finish the setup on Private Packagist.
2237

23-
![GitHub Credentials](/Resources/public/img/docs/integration-setup/github-03-github-credentials.png)
38+
![GitHub Credentials](/Resources/public/img/docs/integration-setup/github-03-github-credentials-20241219.png)
2439

2540
## Finish the Setup
26-
Copy and paste the "Client ID" and "Client Secret" values back into the Private Packagist integration form and submit the form with the "Create Integration" button.
41+
Copy and paste the "Client ID" and "Client Secret" values back into the Private
42+
Packagist integration form and submit the form with the "Create Integration"
43+
button.
44+
45+
![Private Packagist Integration Form](/Resources/public/img/docs/integration-setup/self-hosted/github-04-packagist-form.png)
46+
47+
The GitHub integration will be created and you will be redirected to the admin page.
48+
49+
The new integration will be shown in the list of available integrations, and your users can
50+
now log in to your Private Packagist Self-Hosted installation using their GitHub account.
2751

28-
![Packagist Form](/Resources/public/img/docs/integration-setup/github-04-packagist-form.png)
52+
![Available integrations](/Resources/public/img/docs/integration-setup/self-hosted/github-05-integrations-overview.png)

docs/self-hosted/gitlab-integration-setup.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ If you are using our cloud product at packagist.com, [use this guide](../cloud/g
77
## Initial Setup
88
Hit the "Add Integration" button on the admin page in Private Packagist Self-Hosted to get to the form below.
99

10-
![Add Integration](/Resources/public/img/docs/self-hosted/08-integration.png)
10+
![Add Integration](/Resources/public/img/docs/self-hosted/08-integration-create.png)
1111

1212
To setup a GitLab integration with Private Packagist start by selecting "GitLab" as the platform and enter the URL of your own GitLab server or use <i>https://gitlab.com</i> for the public GitLab server as seen in the example below. A link to setup the oauth application on GitLab will automatically be displayed.
1313

docs/self-hosted/installation.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ Select options for your SMTP server or use the GMail option for a simplified for
7070
![Email Settings](/Resources/public/img/docs/self-hosted/05-email-settings.png)
7171

7272
## Application Startup
73-
Save and apply the settings to start Private Packagist Self-Hosted. Leave the Setup mode enabled.
73+
Save and apply the settings to start Private Packagist Self-Hosted. Leave the Setup Mode enabled.
7474

7575
![Start Application](/Resources/public/img/docs/self-hosted/06-save-start.png)
7676

docs/self-hosted/kubernetes-embedded.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@ or gitlab.com. Follow the instructions to create the respective required identif
118118
* [Authentication with Email Addresses and Passwords](./authentication-email-addresses-passwords-setup.md).
119119

120120

121-
![Add Integration](/Resources/public/img/docs/self-hosted/08-integration.png)
121+
![Add Integration](/Resources/public/img/docs/self-hosted/08-integration-create.png)
122122

123123
#### Selecting Admins
124124
After setting up an integration, you can log in through the top menu. Register an account and pick a username.

docs/self-hosted/kubernetes-helm.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -64,7 +64,7 @@ or gitlab.com. Follow the instructions to create the respective required identif
6464
* [Authentication with Email Addresses and Passwords](./authentication-email-addresses-passwords-setup.md).
6565

6666

67-
![Add Integration](/Resources/public/img/docs/self-hosted/08-integration.png)
67+
![Add Integration](/Resources/public/img/docs/self-hosted/08-integration-create.png)
6868

6969
#### Selecting Admins
7070
After setting up an integration, you can log in through the top menu. Register an account and pick a username.

features/integration-github-bitbucket-gitlab.md

+4-2
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ You can log into Private Packagist using an account on GitHub.com, Bitbucket.org
99

1010
You can then either create a new organization directly synchronized with a GitHub organization, Bitbucket workspace or a GitLab group, or you can enable synchronization for an existing Organization in _Settings_.
1111

12-
![Synchronization](/Resources/public/img/docs/features/Sync-20170306.png)
12+
![Synchronization](/Resources/public/img/docs/features/Sync-20241218.png)
1313

1414
Apart from synchronizing teams, users, and permissions, setting up the integration will simplify the addition of new packages to your Composer repository. When you create a **new repository** on GitHub, Bitbucket, or GitLab, it will be **added as a Composer package automatically** if it contains a _composer.json_ file. If you’d like to add existing repositories as packages, you can do so with the click of a button on the Packages tab in your organization.
1515

@@ -20,7 +20,7 @@ Apart from synchronizing teams, users, and permissions, setting up the integrati
2020
Private Packagist integrates with the following systems:
2121

2222
#### GitHub
23-
* OAuth: Users authenticate on Private Packagist with their GitHub accounts
23+
* OAuth: Users authenticate on Private Packagist with their GitHub accounts. If you use Private Packagist Self-Hosted, first create a GitHub app by following these [steps](../docs/self-hosted/github-integration-setup.md).
2424
* Synchronization:
2525
* Keeps teams, their members, and access permissions in sync with your GitHub organization
2626
* Code Credentials: GitHub App or GitHub API Token
@@ -41,6 +41,7 @@ Private Packagist integrates with the following systems:
4141
* Webhooks: Code changes and releases
4242

4343
#### Bitbucket Data Center / Server
44+
4445
* OAuth: Users authenticate on Private Packagist with their Bitbucket Data Center / Server accounts. Follow [this setup](../docs/cloud/bitbucket-server-integration-setup.md) for Cloud plans or [this setup](../docs/self-hosted/bitbucket-server-integration-setup.md) for Self-Hosted.
4546
* Synchronization:
4647
* Keeps users and access permissions in sync with your Bitbucket Server projects
@@ -65,6 +66,7 @@ Private Packagist integrates with the following systems:
6566
* Webhooks: Code changes and releases
6667

6768
#### AWS CodeCommit
69+
* Code Credentials: Either create HTTPS Git credentials and store it as HTTP Basic credential or grant us access via SSH key
6870
* Webhook:
6971
* Users need to [create an AWS CodeCommit Trigger](https://docs.aws.amazon.com/codecommit/latest/userguide/how-to-notify-sns.html) using the generic hook URL from the package page
7072
* Code changes are available automatically. For releases, you need to select "All repository events" for the events type.

0 commit comments

Comments
 (0)