Registration status
Vendor files
All
state/order*.txt files, and how many of their rows are already provisioned into the DB.| path | rows | registered | remaining |
|---|---|---|---|
| state/order-100.txt | 100 | 100 | 0 |
| state/order-100b.txt | 100 | 100 | 0 |
| state/order-40.txt | 40 | 40 | 0 |
| state/order-50.txt | 50 | 50 | 0 |
| state/order.txt | 10 | 10 | 0 |
| state/order8723568.txt | 100 | 100 | 0 |
| state/order8732102.txt | 100 | 100 | 0 |
| state/order8732132.txt | 1 | 1 | 0 |
| state/order8732154.txt | 10 | 10 | 0 |
| state/order8732261.txt | 1000 | 1000 | 0 |
Accounts in DB, by state
| state | count |
|---|---|
| active | 1482 |
| dead | 8 |
| paused | 14 |
| registered | 7 |
Next batch — what to run
These commands live outside the UI. Run them in a shell from the project root.
# 1) provision. Files are processed sequentially; each dedupes by email # against the DB, so re-runs are safe. Kick these off one after the # other (or chain with && in one shell). python3 register.py --vendor-file state/order.txt --count 8 python3 register.py --vendor-file state/order-40.txt --count 40 python3 register.py --vendor-file state/order-100.txt --count 100 # 2) backfill onboarding for any rows where step-7 tripped python3 onboard.py --concurrency 3 # 3) confirm exit-IP locks python3 audit.py --check proxy-lock # 4) farm.py has hot-reload: new onboarded accounts are picked up every # 60 s without restart. If farm.py is already running, you don't need # to bounce it. If it isn't: python3 farm.py --loop