Export files to Rackspace Cloud Files

A note about URLs

If your container is CDN-enabled, the resulting file.url indicates the path to the file in your CDN container, or is null otherwise.

The storage container URL for this file is always available via file.meta.storage_url.

Parameters

• use

  String / Array of Strings / Objectrequired

  Specifies which Step(s) to use as input.

  • You can pick any names for Steps except ":original" (reserved for user uploads handled by Transloadit)

  • You can provide several Steps as input with arrays:

    "use": [
      ":original",
      "encoded",
      "resized"
    ]
    

  💡 That’s likely all you need to know about use, but you can view advanced use cases:

  › Advanced use cases

  • Step bundling. Some Robots can gather several Step results for a single invocation. For example, 🤖/file/compress would normally create one archive for each file passed to it. If you'd set bundle_steps to true, however, it will create one archive containing all the result files from all Steps you give it. To enable bundling, provide an object like the one below to the use parameter:

    "use": {
      "steps": [
        ":original",
        "encoded",
        "resized"
      ],
      "bundle_steps": true
    }
    

    This is also a crucial parameter for 🤖/video/adaptive, otherwise you'll generate 1 playlist for each viewing quality.
    Keep in mind that all input Steps must be present in your Template. If one of them is missing (for instance it is rejected by a filter), no result is generated because the Robot waits indefinitely for all input Steps to be finished.

    Here’s a demo that showcases Step bundling.

  • Group by original. Sticking with 🤖/file/compress example, you can set group_by_original to true, in order to create a separate archive for each of your uploaded or imported files, instead of creating one archive containing all originals (or one per resulting file). This is important for for 🤖/media/playlist where you'd typically set:

    "use": {
      "steps": [
        "segmented"
      ],
      "bundle_steps": true,
      "group_by_original": true
    }
    

  • Fields. You can be more discriminatory by only using files that match a field name by setting the fields property. When this array is specified, the corresponding Step will only be executed for files submitted through one of the given field names, which correspond with the strings in the name attribute of the HTML file input field tag for instance. When using a back-end SDK, it corresponds with myFieldName1 in e.g.: $transloadit->addFile('myFieldName1', './chameleon.jpg').

    This parameter is set to true by default, meaning all fields are accepted.

    Example:

    "use": {
      "steps": [ ":original" ],
      "fields": [ "myFieldName1" ]
    }
    

  • Use as. Sometimes Robots take several inputs. For instance, 🤖/video/merge can create a slideshow from audio and images. You can map different Steps to the appropriate inputs.

    Example:

    "use": {
      "steps": [
        { "name": "audio_encoded", "as": "audio" },
        { "name": "images_resized", "as": "image" }
      ]
    }
    

    Sometimes the ordering is important, for instance, with our concat Robots. In these cases, you can add an index that starts at 1. You can also optionally filter by the multipart field name. Like in this example, where all files are coming from the same source (end-user uploads), but with different <input> names:

    Example:

    "use": {
      "steps": [
        { "name": ":original", "fields": "myFirstVideo", "as": "video_1" },
        { "name": ":original", "fields": "mySecondVideo", "as": "video_2" },
        { "name": ":original", "fields": "myThirdVideo", "as": "video_3" }
      ]
    }
    

    For times when it is not apparent where we should put the file, you can use Assembly Variables to be specific. For instance, you may want to pass a text file to 🤖/image/resize to burn the text in an image, but you are burning multiple texts, so where do we put the text file? We specify it via ${use.text_1}, to indicate the first text file that was passed.

    Example:

    "watermarked": {
      "robot": "/image/resize",
      "use"  : {
        "steps": [
          { "name": "resized", "as": "base" },
          { "name": "transcribed", "as": "text" },
        ],
      },
      "text": [
        {
          "text"  : "Hi there",
          "valign": "top",
          "align" : "left",
        },
        {
          "text"    : "From the 'transcribed' Step: ${use.text_1}",
          "valign"  : "bottom",
          "align"   : "right",
          "x_offset": 16,
          "y_offset": -10,
        }
      ]
    }
    

• credentials

  Stringrequired

  Please create your associated Template Credentials in your Transloadit account and use the name of your Template Credentials as this parameter's value. They will contain the values for your Cloud Files Container, User, Key, Account type and Data center.

  While we recommend to use Template Credentials at all times, some use cases demand dynamic credentials for which using Template Credentials is too unwieldy because of their static nature. If you have this requirement, feel free to use the following parameters instead: "account_type" ("us" or "uk"), "data_center" ("dfw" for Dallas or "ord" for Chicago for example), "user", "key", "container".

• path

  String ⋅ default: "${file.id}_${file.url_name}"

  The path at which to store the file. This value can also contain Assembly variables.

Demos

• Store uploaded files in a Rackspace Cloud Files container
• Copy files from Amazon S3 to Rackspace Cloud Files

Related blog posts

• Support for Rackspace Cloud Files November 11, 2010
• Rapid Growth and New Features November 12, 2010
• Two Small Feature Updates February 11, 2012
• Assembly Variables Now Available Everywhere April 27, 2012
• Raising prices (for new customers) February 7, 2018