The travis Ruby gem command has two commands, travis encrypt, and travis encrypt-file. travis encrypt encrypts an environment variable, and spits out an encrypted value to put in env/global/secure in the .travis.yml file.
travis encrypt-file encrypts the given file, then uploads the key and iv to the project settings in Travis via the API (which requires a login).
I'm writing an application that encrypts a file for Travis (not using the travis Ruby gem), and I'm wondering if there are any good reasons to upload the encryption key to the Travis project to an environment variable via the API for encrypted files, vs. just encrypting it adding it to the .travis.yml a la travis encrypt, particularly if there are any security concerns from doing it one way over the other.
