2012-02-10 15:36:36 +00:00
|
|
|
# Packagist Update Schedule
|
|
|
|
|
|
|
|
|
|
## How often does Packagist crawl newly added packages?
|
|
|
|
|
|
2012-02-12 21:24:18 +00:00
|
|
|
New packages will be crawled **within ten minutes**.
|
2012-02-10 15:36:36 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
## How often does Packagist crawl existing packages?
|
|
|
|
|
|
|
|
|
|
Existing packages will be crawled **every hour**.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## How often does the Packagist search index update?
|
|
|
|
|
|
2012-02-12 21:24:18 +00:00
|
|
|
The search index is updated **every five minutes**. It will index (or reindex)
|
2012-02-10 15:36:36 +00:00
|
|
|
any package that has been crawled since the last time the search
|
|
|
|
|
indexer ran.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Can Packagist be triggered to recrawl a package (on commit or by other means)?
|
|
|
|
|
|
2012-02-29 14:57:16 +00:00
|
|
|
Yes, you can click the "Force update" button on your package page if you are
|
|
|
|
|
logged in as a maintainer. The recommended way is to set up the GitHub hook,
|
|
|
|
|
you can find the URL and instructions on your Packagist
|
|
|
|
|
[profile](http://packagist.org/profile/) page.
|
