Epycbyte Limits Overview
-
File Uploads: CLI Deployments allow up to 15,000 source files. Exceeding this may cause build failure.
-
Build Time: Maximum allowed time is 45 minutes; exceeding this results in a failed build. Consider using Incremental Static Regeneration (ISR) for faster builds.
-
Proxied Requests: Timeout of 30 seconds applies to external requests. Ensure external servers respond within this timeframe to avoid errors.
-
Real-Time Communication: WebSockets and Serverless Functions are unsupported. Use third-party solutions for real-time features.
-
Analytics and Performance Tools: Specific limits exist for Epycbyte Web Analytics and Speed Insights; refer to the linked documentation for details.
-
Cron Jobs: Limits apply to scheduled tasks. Plan cron jobs during off-peak hours to avoid exceeding caps.
-
Epycbyte Functions: Runtime-specific constraints affect memory, duration, and other resources. Choose appropriate runtimes based on function requirements.
-
Git Repository Integration: Cannot connect projects to Git repositories owned by Git organizations. Use existing teams or create new ones for such repositories.
-
Environment Variables: Adhere to reserved variables and environment variable best practices to avoid issues.
-
Rate Limits:
- Domain Deletion: 60 domains per minute; wait if exceeding.
- Team Deletion: 20 teams per hour; wait if needed.
- Username Changes: 6 changes per week; plan accordingly.
- Builds/Deployments: 32 builds per hour and 100 deployments per day for Hobby plans.