AppleAutoPro Docs

English

简体中文

English

简体中文

Appearance

Installation Guide ​

Before using AppleAutoPro, please make sure you have basic Linux skills (e.g., SSH) and are familiar with technologies such as Docker, MySQL, and PHP. This will help you complete the installation and usage more smoothly.

If you are unable to perform the installation yourself, we offer a paid installation service for your convenience.

System Requirements ​

  • Recommended System: Debian 11 or higher, Ubuntu 20.04 or higher
  • Not Recommended: CentOS

System Architecture Overview ​

This project uses Docker Compose for one-click deployment. The frontend and backend are already integrated.

1. Frontend (Management Interface) ​

  • Provides a visual web panel
  • Supports account management, task management, log viewing, and more

2. Backend (Task Execution Module) ​

  • Uses a queue-based multithreading model to execute tasks efficiently
  • Performs account checking tasks

Resource Requirements ​

  • Memory: Each backend thread consumes about 400 MB of RAM during task execution, and about 150 MB when idle.
  • Bandwidth: Each task run (with all detection features enabled) uses approximately 40 MB of traffic.
  • Execution Model: Tasks are executed sequentially in a queue-based model. You can configure the maximum concurrency. The backend supports horizontal scaling and multi-instance deployment.

Network Requirements ​

  • IP: Some IP ranges may be blacklisted by Apple. It is recommended to use native IPs or dynamic IPs.
  • For more details, see Network Requirements.
  • The program supports proxy pool execution. If you need to install your own proxy, see Install HTTP Proxy.

IP Rate Limiting and Risk Control ​

Apple applies strict risk control on outbound IPs. Using the same IP for frequent logins or unlock tasks in a short period can trigger rate limiting or temporary blocks.

  • Cooldown: After one account task completes on a single IP, wait at least 10 minutes before running the next task on that IP.
  • IP-to-account ratio: Keep the number of available IPs roughly 1:1 with the number of managed accounts. If you have many accounts, add more IPs/proxies or lower backend concurrency to avoid chaining multiple accounts through one IP.

Note: If you have any questions or need further technical support, please consult the official documentation or contact the maintainers.