|
| 1 | +# Troubleshooting |
| 2 | +## Private Packagist |
| 3 | + |
| 4 | +### New versions do not appear instant |
| 5 | + |
| 6 | +Depending on how the package has been added to Private Packagist it may take a different amount of time until |
| 7 | +new or updated versions appear in Private Packagist. The times of how long it can take for new versions to appear |
| 8 | +in Private Packagist can be found in the section below. In case the version does not appear within the mentioned time frame |
| 9 | +the update log which can be accessed on the package page via "View Log" can contain information about why a certain versions |
| 10 | +was not picked up by Private Packagist e.g. the composer.json file is invalid. |
| 11 | + |
| 12 | +##### Packages added from packagist.org |
| 13 | + |
| 14 | +New or updated versions for packages that are mirrored from packagist.org appear within seconds or minutes |
| 15 | +after the update is available on packagist.org. The time from push to the VCS repository until it appears on Private Packagist |
| 16 | +depends on whether the package has a working webhook set up on packagist.org and how long it takes for GitHub/GitLab/Bitbucket |
| 17 | +to notify packagist.org. |
| 18 | + |
| 19 | +##### Packages added to Private Packagist either with a credential or via synchronization |
| 20 | + |
| 21 | +For packages which are imported from GitHub/GitLab/Bitbucket where we have access to the respective API with credentials |
| 22 | +there we attempt to set up webhooks to get notified about new versions. This means that new versions will appear within |
| 23 | +seconds or a few minutes after the VCS repository push. |
| 24 | + |
| 25 | +##### All other packages |
| 26 | + |
| 27 | +For all other packages, this includes repositories to which we have been granted via ssh key, repositories that are hosted on |
| 28 | +other platforms than GitHub, GitLab and Bitbucket, packages added from a third party mirrored repository other than packagist.org |
| 29 | +and repositories that have been added without a credential, Private Packagist does not get notified about new versions. Therefore |
| 30 | +we run updates on regular intervals once every three hours. This means new or updated versions will not appear instant on Private Packagist. |
0 commit comments