You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Alternatively you can copy the SSH public key for your organization on the same
13
13
14
14
### Add packages
15
15
16
-
If your organization is synchronized Private Packagist will have created packages for all of your private repositories containing a composer.json. Otherwise or if you would like to add additional packages you can add them in the _Packages_ section of your organization with the Add button. Follow the instructions to pick the right option for your package.
16
+
If your organization is synchronized Private Packagist will have created packages for all of your private repositories containing a composer.json. Otherwise or if you would like to add additional packages you can add them in the _Packages_ section of your organization with the *Add* button. Follow the instructions to pick the right option for your package.
17
17
18
18
### Configure your project to use Private Packagist
Copy file name to clipboardExpand all lines: docs/cloud/bitbucket-server-oauth1-integration-setup.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,8 +26,8 @@ To allow your users to authenticate to Private Packagist with their Bitbucket Da
26
26
first need to create an integration in Private Packagist. This document walks you through the required steps.
27
27
28
28
## Open the Add Integration form
29
-
From the organization settings page, select the "Integrations" subtab.
30
-
Hit the "Add Integration" button on the integrations listing page to get to the form below.
29
+
From the organization settings page, select the *Integrations* subtab.
30
+
Hit the *Add Integration* button on the integrations listing page to get to the form below.
31
31
To set up a Bitbucket Data Center / Server integration with Private Packagist, start by selecting "Bitbucket Data Center / Server"
32
32
as the platform, enter the URL of your on-premise Bitbucket Data Center / Server into the base URL field and select OAuth 1 as the OAuth version as seen in the example below.
33
33
@@ -38,17 +38,17 @@ Submit the form to see the additional information.
Click on the link to setup an Application Link on Bitbucket Data Center / Server. You will need the "Client Id" and the "Public Key" shown in the form.
41
+
Click on the link to setup an Application Link on Bitbucket Data Center / Server. You will need the *Client Id* and the *Public Key* shown in the form.
42
42
43
43
44
44
45
45
For Bitbucket Data Center versions 7.21 and newer, select "Atlassian product" and not "External application" to be able to set up an OAuth1 link.
46
46
47
-
After you hit the button to create a new Application Link a configuration window may appear. If it does, verify that the url matches the "Application URL for Link" (_https://packagist.com_) and hit "Continue", otherwise skip this step.
47
+
After you hit the button to create a new Application Link a configuration window may appear. If it does, verify that the url matches the *Application URL for Link* (_https://packagist.com_) and hit *Continue*, otherwise skip this step.
48
48
49
49
50
50
51
-
Now setup a "Generic Application". The only field required is the "Application Name". Submit the form to finish creating the Application Link.
51
+
Now setup a *Generic Application*. The only field required is the *Application Name*. Submit the form to finish creating the Application Link.
52
52
53
53
54
54
@@ -58,12 +58,12 @@ Click on the pen icon to the right of the application you just created to edit t
58
58
59
59
60
60
61
-
This is where we will need the "Client ID" and the "Public Key" that were previously generated on the Private Packagist integration form.
62
-
Enter the "Client ID" into the "Consumer Key" field, make sure the entire content of the "Public Key" field gets copied and the "Consumer Callback" field stays empty.
61
+
This is where we will need the *Client ID* and the *Public Key* that were previously generated on the Private Packagist integration form.
62
+
Enter the *Client ID* into the *Consumer Key* field, make sure the entire content of the *Public Key* field gets copied and the *Consumer Callback* field stays empty.
63
63
Submit the form and go back to the list of integrations in Private Packagist.
64
64
65
65
### Share the Bitbucket login link
66
-
The final step is sharing your organization-specific login link with your users. Look for the "Login link" button next to
66
+
The final step is sharing your organization-specific login link with your users. Look for the *Login link* button next to
67
67
your newly created Bitbucket Data Center / Server integration on the integrations page, and copy the URL.
68
68
69
69
Copy file name to clipboardExpand all lines: docs/dependabot-for-private-packagist.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ This guide explains how to configure and set up Dependabot if you want to use it
8
8
9
9
## Enable Dependabot in GitHub
10
10
11
-
Start in your GitHub repository and go to “Settings”. In the “Security” section of the sidebar go to “Code security and analysis”, where you can enable Dependabot. In this process, you will create a dependabot.yaml [as shown as below](#dependabotyaml). Follow [this guide on GitHub](https://docs.github.com/en/code-security/getting-started/dependabot-quickstart-guide#enabling-dependabot-for-your-repository) for the complete steps to enable Dependabot.
11
+
Start in your GitHub repository and go to *Settings*. In the *Security* section of the sidebar go to *Code security and analysis*, where you can enable Dependabot. In this process, you will create a dependabot.yaml [as shown as below](#dependabotyaml). Follow [this guide on GitHub](https://docs.github.com/en/code-security/getting-started/dependabot-quickstart-guide#enabling-dependabot-for-your-repository) for the complete steps to enable Dependabot.
Replace the Composer URL `https://repo.packagist.com/acme/` with your organization's Composer URL on packagist.com. The example URL is for the organization named `acme`.
39
39
40
-
To grant Dependabot access to the packages on Private Packagist, you need to provide the secret `PRIVATE_PACKAGIST_AUTH_TOKEN` to your GitHub repository. In Settings, under the section “Security,” there is a “Secrets and Variables” page for Dependabot.
40
+
To grant Dependabot access to the packages on Private Packagist, you need to provide the secret `PRIVATE_PACKAGIST_AUTH_TOKEN` to your GitHub repository. In *Settings*, under the section *Security*, there is a *Secrets and Variables* page for Dependabot.
Now, on Private Packagist, create an authentication token with update access under “Settings” and “Authentication Tokens”. Copy the secret token into the GitHub form.
44
+
Now, on Private Packagist, create an authentication token with update access under *Settings* and *Authentication Tokens*. Copy the secret token into the GitHub form.
45
45
46
46
## Troubleshooting
47
47
48
-
To check if Dependabot is able to access your packages, navigate to “Insights” on your GitHub repository, then “Dependency Graph” and then activate the tab “Dependabot”.
48
+
To check if Dependabot is able to access your packages, navigate to *Insights* on your GitHub repository, then *Dependency Graph* and then activate the tab *Dependabot*.
Mirrored packages show up in your Private Packagist search results, your [License Review](../features/license-review.d), and can be installed from your Private Packagist repository with Composer. Their distribution files are cached in your Private Packagist organization to make downloads redundant and faster.
7
7
8
-
To setup credentials for a repository, “Magento Marketplace” in our example, head to Settings > Manage Credentials in your Private Packagist organization. Afterwards you can add a new mirrored third party repository under Settings as well. From then on packages can be manually or automatically mirrored based on your configuration.
8
+
To setup credentials for a repository, "Magento Marketplace" in our example, head to *Settings > Manage Credentials* in your Private Packagist organization. Afterwards you can add a new mirrored third party repository under *Settings* as well. From then on packages can be manually or automatically mirrored based on your configuration.
9
9
10
10
## Magento Marketplace Walkthrough
11
-
Start by hitting “Manage Credentials” in your organizations settings. My organization is called “ACME Company”.
11
+
Start by hitting *Manage Credentials* in your organizations settings. My organization is called "ACME Company".
Next enter a description, I’m going with “Magento Marketplace Credentials”, and select “Magento Marketplace” as the authentication type. The domain “repo.magento.com” will be filled in automatically. Now we need the Magento Marketplace Public and Private Key, we’ll click on “My Access Keys” to get to the Magento Marketplace website.
15
+
Next enter a description, I'm going with "Magento Marketplace Credentials", and select "Magento Marketplace" as the authentication type. The domain "repo.magento.com" will be filled in automatically. Now we need the Magento Marketplace Public and Private Key, we'll click on *My Access Keys* to get to the Magento Marketplace website.
Make sure you’re on the Magento 2 Access Keys page, and then copy and paste the Private and Public keys into the respective fields on Private Packagist. Once you’re done, hit “Create” on the Private Packagist Credentials page.
19
+
Make sure you're on the Magento 2 Access Keys page, and then copy and paste the Private and Public keys into the respective fields on Private Packagist. Once you're done, hit *Create* on the Private Packagist Credentials page.
Pick a name for the repository, I picked “Magento Marketplace”, enter the URL “https://repo.magento.com” and pick the credentials we just set up for authentication with this repository. You can choose whether you would like packages to be mirrored automatically when someone tries to access them through composer update, or if you would like to add them yourself manually.
I’m going to enter just one package for the demo, but you can add as many as you like here. I’m going with “magento/module-catalog”. Make sure to select the “Magento Marketplace” Mirror repository underneath, and hit “Add”.
35
+
I'm going to enter just one package for the demo, but you can add as many as you like here. I'm going with "magento/module-catalog". Make sure to select the "Magento Marketplace" Mirror repository underneath, and hit *Add*.
Copy file name to clipboardExpand all lines: docs/self-hosted/authentication-email-addresses-passwords-setup.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
## Setup
5
5
By default, authentication with email addresses and passwords is disabled. If possible, we recommend setting up authentication with your installation of [GitHub (Enterprise)](./github-integration-setup.md), [Bitbucket.org](./bitbucket-integration-setup.md), [Bitbucket Data Center / Server](./bitbucket-server-integration-setup.md), or [GitLab](./gitlab-integration-setup.md) using OAuth instead.
6
6
7
-
Navigate to the "Global Configuration" section from the admin page to get to the form below.
8
-
Enable login and account registration with email addresses and passwords by selecting the option in the form and submitting the form via the "Update configuration" button.
7
+
Navigate to the *Global Configuration* section from the admin page to get to the form below.
8
+
Enable login and account registration with email addresses and passwords by selecting the option in the form and submitting the form via the *Update configuration* button.
0 commit comments