@uppy/companion

Companion

Companion is a server integration for Uppy file uploader.

It handles the server-to-server communication between your server and file storage providers such as Google Drive, Dropbox, Instagram, etc. Companion is not a target to upload files to. For this, use a https://tus.io server (if you want resumable) or your existing Apache/Nginx server (if you don't). See here for full documentation

Install

npm install @uppy/companion

If you don't have a Node.js project with a package.json you might want to install/run Companion globally like so: [sudo] npm install -g @uppy/companion@0.17.4 (best check the actual latest version, and use that, so (re)installs are reproducible, and upgrades intentional).

Usage

companion may either be used as pluggable express app, which you plug to your already existing server, or it may simply be run as a standalone server:

Plug to already existing server

var express = require('express')
var bodyParser = require('body-parser')
var session = require('express-session')
var companion = require('@uppy/companion')

var app = express()
app.use(bodyParser.json())
app.use(session({secret: 'some secrety secret'}))
...
// be sure to place this anywhere after app.use(bodyParser.json()) and app.use(session({...})
const options = {
  providerOptions: {
    google: {
      key: 'GOOGLE_KEY',
      secret: 'GOOGLE_SECRET'
    }
  },
  server: {
    host: 'localhost:3020',
    protocol: 'http',
  },
  filePath: '/path/to/folder/'
}

app.use(companion.app(options))

To enable companion socket for realtime feed to the client while upload is going on, you call the socket method like so.

...
var server = app.listen(PORT)

companion.socket(server, options)

Run as standalone server

Please ensure that the required env variables are set before runnning/using companion as a standalone server. See.

$ companion

If you cloned the repo from GitHub and want to run it as a standalone server, you may also run the following command from within its directory

npm start

Run as a serverless function

Companion can be deployed as a serverless function to AWS Lambda or other cloud providers through serverless. Check this guide to get started.

After you have cloned the repo go inside examples/serverless:

cd examples/serverless

You can enter your API Keys inside the serverless.yml file:

INSTAGRAM_KEY: <YOUR_INSTAGRAM_KEY>
INSTAGRAM_SECRET: <YOUR_INSTAGRAM_SECRET>

When you are all set install the dependencies and deploy your function:

npm install && sls deploy

Deploy to heroku

Companion can also be deployed to Heroku

mkdir uppy-companion && cd uppy-companion

git init

echo 'export COMPANION_PORT=$PORT' > .profile
echo 'node_modules' > .gitignore
echo '{
  "name": "uppy-companion",
  "version": "1.0.0",
  "scripts": {
    "start": "companion"
  },
  "dependencies": {
    "@uppy/companion": "^0.17.0"
  }
}' > package.json

npm i

git add . && git commit -am 'first commit'

heroku create

git push heroku master

Make sure you set the required environment variables.

See full documentation

Changelog

1.8.0

Released: 2020-01-15

This release adds Korean and Vietnamese localizations, fixes bugs, and significantly improves the performance of adding and removing lots of files. More performance improvements are on the way in the next few releases, too! Thanks to all contributors listed below.

| Package | Version | Package | Version | |-|-|-|-| | @uppy/aws-s3-multipart | 1.4.0 | @uppy/onedrive | 0.1.4 | | @uppy/aws-s3 | 1.4.1 | @uppy/progress-bar | 1.3.4 | | @uppy/companion | 1.8.0 | @uppy/provider-views | 1.5.2 | | @uppy/core | 1.7.1 | @uppy/react | 1.4.2 | | @uppy/dashboard | 1.5.2 | @uppy/robodog | 1.4.2 | | @uppy/drag-drop | 1.4.2 | @uppy/status-bar | 1.4.2 | | @uppy/dropbox | 1.3.5 | @uppy/thumbnail-generator | 1.5.2 | | @uppy/facebook | 0.2.2 | @uppy/transloadit | 1.4.2 | | @uppy/file-input | 1.4.2 | @uppy/tus | 1.5.2 | | @uppy/form | 1.3.5 | @uppy/url | 1.4.2 | | @uppy/golden-retriever | 1.3.4 | @uppy/utils | 2.1.2 | | @uppy/google-drive | 1.3.5 | @uppy/webcam | 1.5.1 | | @uppy/informer | 1.3.4 | @uppy/xhr-upload | 1.4.2 | | @uppy/instagram | 1.3.5 | uppy | 1.8.0 | | @uppy/locales | 1.11.0 | - | - |

• @uppy/aws-s3-multipart: add optional headers for signed url (@ardeois, #1985)
• @uppy/aws-s3: fix crash when S3 response does not have a Content-Type header (@roenschg, #2012)
• @uppy/companion: also pass metadata to getKey for multipart S3 uploads (@goto-bus-stop, #2022)
• @uppy/companion: dependency updates (@goto-bus-stop, #1983)
• @uppy/companion: rename internal S3 upload functions for clarity (@goto-bus-stop, fec7d7d)
• @uppy/core: improve performance of adding and removing files (@goto-bus-stop, #1949)
• @uppy/locales: add Korean (@jdssem, #1986)
• @uppy/locales: add Vietnamese (@thanhthot, #2010)
• @uppy/locales: update French translations (@olemoign, #2023)
• @uppy/provider-views: improve instagram video thumbnail display (@arturi, 1d7a584)
• @uppy/react: use componentDidUpdate instead of componentWillReceiveProps (@cryptic022, #1999)
• @uppy/thumbnail-generator: fix strict mode compatibility (@rlebosse, #1995)
• @uppy/tus: update TusOptions typings (@darthf1, #1989)
• @uppy/xhr-upload: do not emit limit warning if an existing rate limit queue was passed (@goto-bus-stop, 3c1a2af)
• @uppy/xhr-upload: free item from rate limit queue when upload times out (@rtaieb, #2018)
• examples: add npm run example $examplename script (@goto-bus-stop, 7b2283d)