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
If you have private repositories on Bitbucket/Gitlab or a Satis/Toran Proxy with private dependencies,
9
-
you can use SSH Keys to access them during your build. Simply go to the *Build Settings* of your pipeline
10
-
configuration and enter your private SSH Keys to make them available in every container of your build.
8
+
9
+
10
+
If you need to use private repositories on Bitbucket/Gitlab or a Satis/Toran Proxy with private dependencies, ContinuousPHP offer several ways to reach your goal.
11
+
12
+
First, simply go to the *Build Settings* of your pipeline configuration and enter your private SSH Keys to make them available in every container of your build.
Notice that despite of using directly your git provider url (i.e bitbucket.org, gitlab.com ...) as a hostname, you need to use a specific syntax *keyname-bb* where:
78
58
79
-
After creating the Satis configuration file, you need to tell Satis create the repositories :
59
+
****keyname*** refers to the key name specified in your pipeline settings
The below table lists each prefix associated to git hosting services.
84
63
85
-
When this command finishes, we have a new directory `my-mirrored-dependencies` with two files: `packages.json` and `index.html`.
86
-
`packages.json` will be read by *Composer* to determine what packages the repository offers.
87
-
`index.html` is a static HTML file with information about the repository.
88
-
It also contains the dist directory with all packages so they won’t have to be downloaded from GitHub anymore.
89
64
90
-
### Use Satis in Composer
65
+
<table>
66
+
<tr>
67
+
<td>bb</td><td>bitbucket.org</td>
68
+
</tr>
69
+
<tr>
70
+
<td>gh</td><td>github.com</td>
71
+
</tr>
72
+
</table>
91
73
92
-
To use our new Satis Proxy with *Composer* we have to include it in our `composer.json` like this :
93
74
94
-
```
95
-
{
96
-
"repositories": [
97
-
{
98
-
"type": "composer",
99
-
"url": "http://my-satis-address.com"
100
-
}
101
-
],
102
-
...
103
-
}
104
-
```
75
+
### ***Only for Bitbucket*** alternatively add ContinuousPHP deploy key to your private library
76
+
77
+
For instance, you want to build the [email protected]:account_of_project/project which depends on the library git@library_hosting_service:account_of_library/library.<br/>
78
+
Then you can get the deploy key used by ContinuousPHP and add it to your library repository.
## Composer fails while installing additional libraries
11
+
12
+
If you see a "RuntimeException" message while composer installs additional librairies, please refer to this [section](./credentials-authentication/ssh.md) about SSH keys settings.
13
+
14
+
## ContinuousPHP cannot clone my project
15
+
16
+
If ContinuousPHP is not able to clone your project, that is probably due to an unwanted removal of the ContinuousPHP deployment key from your git provider. So you can try to reset hooks.<br/>
17
+
The associated button can be found in your pipeline settings as described on the below screenshot.
excerpt: "Satis configuration support by continuousphp"
7
+
---
8
+
9
+
10
+
## Using private repositories from Satis
11
+
12
+
Using SSH Keys to authenticate, you can use your own Satis Proxy to install private dependencies with *Composer*. Let's create an example of how to mirror repositories with Satis and then use them with *Composer*.
0 commit comments