Merlijn Vos 07956e25e2 @uppy/companion: pass fetched origins to window.postMessage() (#5529) 4 月之前
..
bin 10bc79574e lerna link convert (#1730) 5 年之前
infra 34c78e9093 meta: run Prettier on existing files (#4713) 1 年之前
output e82f828d19 companion: smaller heroku deployment (#2845) 4 年之前
src 07956e25e2 @uppy/companion: pass fetched origins to window.postMessage() (#5529) 4 月之前
test d6d940c6b2 Enable CSRF protection in grant (OAuth2) (#5504) 5 月之前
.gitignore a47090c2c6 meta: fix `yarn build:clean` 1 年之前
.npmignore e65f2b0397 add `.npmignore` files to ignore .gitignore when packing (#3380) 3 年之前
ARCHITECTURE.md 7d6937300a meta: enable prettier for markdown (#5133) 11 月之前
CHANGELOG.md e07c83bebe Release: uppy@4.8.0 (#5541) 4 月之前
KUBERNETES.md 7d6937300a meta: enable prettier for markdown (#5133) 11 月之前
LICENSE 9a841f693a refactor: rename service-dog -> companion 6 年之前
Makefile 9a841f693a refactor: rename service-dog -> companion 6 年之前
README.md 7d6937300a meta: enable prettier for markdown (#5133) 11 月之前
env_example 7c174e85b7 @uppy/companion: add `s3.forcePathStyle` option (#5066) 9 月之前
heroku.yml fee5ad917f Fix Companion deploys (#3388) 3 年之前
nodemon.json 34c78e9093 meta: run Prettier on existing files (#4713) 1 年之前
package.json 8654e9822f Release: uppy@4.9.0 (#5553) 4 月之前
tsconfig.json a565c3e4a0 @uppy/companion: bump Node.js version support matrix (#5035) 1 年之前

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