Panelica Community Forum
Welcome to the official Panelica Community Forum — the central hub for server administrators, developers, and hosting professionals. Register a free account today to access technical discussions, product announcements, feature requests, and direct support from the Panelica team. Be part of the growing community shaping the future of server management.
Solved deploy işleminde tüm paketler sıfırdan indirildiği için 429 hatası dönüyor github
- Thread starter tailadmin
- Start date
Fixed. The deploy was re-downloading every Composer/npm package from scratch on each run, which hit GitHub's 60-request/hour unauthenticated limit (HTTP 429) and then blew the 300s step timeout when you switched to --prefer-source.
Pipeline steps now use a persistent per-account package cache (COMPOSER_CACHE_DIR / npm_config_cache under your home) that survives between deploys, so the second run is a near-no-op instead of a full re-download. Composer will also read a GitHub token from the step environment (GITHUB_TOKEN) to lift the limit from 60 to 5000/hour if you prefer. You can also raise the step timeout in the pipeline step settings. Ships in the next update.
Pipeline steps now use a persistent per-account package cache (COMPOSER_CACHE_DIR / npm_config_cache under your home) that survives between deploys, so the second run is a near-no-op instead of a full re-download. Composer will also read a GitHub token from the step environment (GITHUB_TOKEN) to lift the limit from 60 to 5000/hour if you prefer. You can also raise the step timeout in the pipeline step settings. Ships in the next update.