Antoine du Hamel 4028a6d16e @uppy/companion: coerce `requestUrl` to a string (#5128) 1 year ago
..
bin 10bc79574e lerna link convert (#1730) 5 years ago
infra 34c78e9093 meta: run Prettier on existing files (#4713) 1 year ago
output e82f828d19 companion: smaller heroku deployment (#2845) 4 years ago
src 4028a6d16e @uppy/companion: coerce `requestUrl` to a string (#5128) 1 year ago
test fbfca41795 Fix companion dns and allow redirects from http->https again (#4895) 1 year ago
.gitignore a47090c2c6 meta: fix `yarn build:clean` 1 year ago
.npmignore e65f2b0397 add `.npmignore` files to ignore .gitignore when packing (#3380) 3 years ago
ARCHITECTURE.md 35812ca378 Companion: rewrite `request` and `purest` to `got` (#3953) 2 years ago
CHANGELOG.md 3deb64b34a Release: uppy@3.24.1 (#5069) 1 year ago
KUBERNETES.md 41b8563ae2 @uppy/companion: add S3 prefix env variable (#4320) 2 years ago
LICENSE 9a841f693a refactor: rename service-dog -> companion 6 years ago
Makefile 9a841f693a refactor: rename service-dog -> companion 6 years ago
README.md 4bdfbe7c48 Merge stable branch 2 years ago
env_example 41b8563ae2 @uppy/companion: add S3 prefix env variable (#4320) 2 years ago
heroku.yml fee5ad917f Fix Companion deploys (#3388) 3 years ago
nodemon.json 34c78e9093 meta: run Prettier on existing files (#4713) 1 year ago
package.json 3deb64b34a Release: uppy@3.24.1 (#5069) 1 year ago
tsconfig.json 588bfb515e meta: prettier 3.0.3 -> 3.2.4 (#4889) 1 year ago

README.md

Companion

Build Status

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@1.x (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 existing server, or it may also be run as a standalone server:

Plug to an existing server

import express from 'express'
import bodyParser from 'body-parser'
import session from 'express-session'
import companion from '@uppy/companion'

const 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: {
    drive: {
      key: 'GOOGLE_KEY',
      secret: 'GOOGLE_SECRET',
    },
  },
  server: {
    host: 'localhost:3020',
    protocol: 'http',
  },
  filePath: '/path/to/folder/',
}

const { app: companionApp } = companion.app(options)
app.use(companionApp)

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

// ...
const server = app.listen(PORT)

companion.socket(server)

Run as standalone server

Please make sure 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

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": "latest"
  }
}' > 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