Yokusō

DigitalOcean Spaces proxy for Dropshare, using OpenResty.
Yokusō makes it possible to use a private DigitalOcean Space with Dropshare, without needing to store the API keys on your device.
It also caches the requests, to serve the files you upload faster.

Usage

Running the service

To run Yokusō, it's recommended to use Docker. To start off, build the container:

docker build -t yokuso:latest .

You can now run it with the following command:

docker run \
  -p 80:80 \
  -v /var/cache/nginx:/var/cache/nginx \
  -e SPACES_REGION="<SPACES_REGION>" \
  -e ACCESS_KEY_ID="<SPACES_ACCESS_KEY>" \
  -e SECRET_ACCESS_KEY="<SPACES_SECRET_KEY>" \
  -e SPACES_ENDPOINT="<SPACES_URL>" \
  -e ROOT_REDIRECT="http://google.com" \
  -e CLIENT_ACCESS_KEY_ID="<DROPSHARE_ACCESS_KEY>" \
  -e CLIENT_SECRET_ACCESS_KEY="<DROPSHARE_ACCESS_KEY>" \
  yokuso:latest

Configuring Dropshare

You can configure Dropshare by adding a Custom S3 API Compliant Connection.

If you are not using path-style URLs, Yokusō will need to run on a subdomain. Set the server in drop share to the main domain, and bucket name to the subdomain (e.g. if Yokusō is running on dump.dmarby.se, the server would be dmarby.se, and the bucket name would be dump.

If you are using path-style URLs, set the server to the domain where Yokusō is running, and the bucket name to anything.

For access key and secret key, enter the values you specified in CLIENT_ACCESS_KEY_ID and CLIENT_SECRET_ACCESS_KEY above.

Thanks to

• Kamal Nasser for making the error page.
• Moriyoshi Koizumi for their work extending api-gateway-aws.
• Hector Castro for creating docker-s3-proxy-cache which inspired this project.