ar.io DocumentationBundler service
Uploads go through Turbo: an upload service that accepts signed data items, and a payment service that answers balance, price and top-up questions. The two belong to the same network, and ario-deploy configures them together.
| When to use | Flags |
|---|---|
| Default (production) | none: https://upload.ardrive.io and https://payment.ardrive.io |
| Development sandbox | --dev |
| Custom or self-hosted services | --uploader \<url\> and --payment-url \<url\> |
--dev selects both sandbox services (https://upload.services.ar-io.dev and https://payment.services.ar-io.dev) and testnet RPCs for --on-demand. Passing the sandbox URL to --uploader alone does the same. A custom --uploader without --payment-url keeps the production payment service and prints a warning, since balance checks and top-ups go there.
ario-deploy upload --wallet ./wallet.json --deploy-folder ./dist --devThe free upload limit is read from the upload service, so it follows the network: 105 KiB per item in production, 5 MiB in the sandbox.
A --dev upload is not permanent. It goes to the Turbo sandbox for testing, production gateways do not serve it, and the result output says so. Never switch to --dev to get past an error on production: the URL it prints does not work as a permanent site.
How is this guide?