Bunny Launcher

Purge

When new content is transferred, your old and outdated content may still be served to users. This command purges your entire pull zone cache so you can ensure that your new content will be served.

Usage

bunny-transfer purge [options] <location...>

Examples

bunny-transfer purge my-pull-zone
bunny-transfer purge my-pull-zone 643475

  • Name
    location
    Type
    string | number
    Description

    Location

    For the purge command, the location can be:

    • A pull zone name like my-storage-zone
    • A pull zone id like 643475

    Locations are positional arguments, and you can specify as many locations as you want. At least one location must be specified.

    Please be careful specifying locations for the purge command, since all pull zone caches will be purged. If you are not using a storage zone as your origin, your origin may experience a heavy load, slow performance, and additional costs. If your assets are no longer on your origin, they will be lost.

  • Name
    --access-key, -k
    Type
    uuid
    Description

    Access Key

    To find your account API Access Key, please visit either:

    • The new Dashboard > Profile picture > Edit account details > API Key
    • The old Panel > Account > API

    All account API Access Keys are in uuid format, such as c24347cf-1bc0-4900-8d60-86b1c7701f53.

    Please use your account API Access Key, not the Password or ReadOnlyPassword of your storage zone.

    Please read the authentication guide to learn more about Access Key types.

  • Name
    --profile, -p
    Type
    string
    Description

    Profile

    Your profile is any easy-to-remember name that you gave to reference your API Access Key. By saving an API Access Key under a profile, you can use that profile to easily select, change, and remove your API Access Key.

    If you only have one profile, that one profile is your default profile and will be automatically selected for all of your commands. When possible, commands will automatically select profiles based on the storage zones, pull zones, dns zones, and linked hostnames in an account.

    If you have multiple profiles and a profile cannot be inferred, then specifying the profile will tell the command which profile it should use. A specified profile name will override all inference, unless the environment variable BUNNY_ACCESS_KEY or the command line flag --access-key is provided.

  • Name
    --shared-credentials-file, -c
    Type
    file-path
    Description

    Shared Credentials File

    All profiles are saved by default in ~/.bunny/credentials.

    The shared credentials file follows the TOML v1.0.0 format specification.

    Each profile consists of a:

    • profile
    • accessKey
    • email
    • id
    • name (optional)

    Shared Credentials File sample

    [personal]
accessKey = "c24347cf-1bc0-4900-8d60-86b1c7701f53"
email = "johndoe@example.com"
id = "31141ed7-9a4c-48b3-9910-676f9c999d70"

[business]
accessKey = "85e2e568-dc73-47c2-8530-ce8f8f42fe6c"
email = "johndoe@company.com"
id = "5552c462-bde1-4a41-88ed-d8c1bc1c51bc"
name = "John Doe"