Configure Redropp

Redropp can be configured with environment variables or with a configuration file.

Environment variables

Use the following template to configure Redropp with environment variables.

# Name/title of this instance
TITLE=

# Public URL
URL=

# Drop settings: per-user quota
# DROP_QUOTA=10G
# DROP_DELAYS=1d *7d 30d 90d

# SMTP information, read the CURL documentation for supported URLs: https://everything.curl.dev/usingcurl/smtp.html
SMTP_URL=
SMTP_USERNAME=
SMTP_PASSWORD=
SMTP_FROM=

# S3 location should look something like this: https://sos-de-fra-1.exo.io/bucket
S3_LOCATION=
S3_ACCESS_KEY_ID=
S3_SECRET_ACCESS_KEY=

# Internal authentication settings
# AUTH_INTERNAL=Yes
# AUTH_REGISTER=Yes

# Configure SSO support
# SSO_TITLE=
# SSO_URL=https://dev-stpsilwgnjk561dj.eu.auth0.com
# SSO_CLIENT_ID=r11Ah7sLNB0AN5FphbRCkNVEyK7XsQ9i
# SSO_CLIENT_SECRET=sTd6h6TywNolfTnHGKBDE37ys6rmZCnQabNvkvBmVZqOKb5Ncpn75ELkTpfp-wma

Environment variables are limited. Some settings (such as customization, multiple SSO providers) can only be changed with a configuration file.

Configuration file

You can create a default configuration file with the following command:

mkdir config
docker run koromix/redropp:latest /app/redropp init > config/redropp.ini

You must configure mandatory settings (title, URL, S3) inside config/redropp.ini before you can run Redropp.

Run Docker image

Manual command

Run the most recent release with the following command:

mkdir -p data
docker run --env-file=ENV -p 8894:80 -v $PWD/data:/data koromix/redropp:latest

Once Redropp is running, open http://localhost:8894/ in your browser. That's it!

This docker command (and the Docker Compose file below) assumes the use of an environment file (named ENV).

In order to use a configuration file (such as config/redropp.ini), you need to mount the config directory, like this:

docker run -p 8894:80 -v $PWD/data:/data -v $PWD/config:/config koromix/redropp:latest

Docker Compose

Here is a sample docker-compose.yml file for use with Docker Compose:

services:
  redropp:
    container_name: redropp
    image: koromix/redropp:latest

    restart: on-failure:3

    env_file: ENV

    ports:
      - 8894:80
    volumes:
      - ./data:/data
      # - ./config:/config

It is recommended to use a specific version tag instead of latest and update manually, even though it is used in the documentation to make things simpler.

Podman Quadlet

Here is a sample Quadlet unit file for use with Podman Quadlet:

[Unit]
Description=Redropp file transers
After=local-fs.target

[Service]
EnvironmentFile=/srv/redropp/ENV

[Container]
Image=docker.io/koromix/redropp:latest
PublishPort=8894:80
Volume=/srv/redropp/data:/data
# Volume=/srv/redropp/config:/config

[Install]
WantedBy=multi-user.target

This unit stores the database in /srv/redropp/data. Change the corresponding Quadlet settings if needed. Make sure the data directory exists.

Save this file somewhere the quadlet systemd generator can find it, such as /etc/containers/systemd/redropp.container.

Start it with the following commands:

systemctl daemon-reload
systemctl start redropp.service

Development image

Development images are regularly pushed to the Docker Hub with the dev tag, use it with the following command:

docker run --env-file=/path/to/env/file -p 8894:80 koromix/redropp:dev

Use this for evaluation only, please don't run this in production!

Reverse proxy

NGINX

Edit your NGINX config (directly or in a server file in /etc/nginx/sites-available) to make it work as a reverse proxy for Redropp.

The server block should you something like this:

server {
    # ...

    location / {
        proxy_http_version 1.1;
        proxy_buffering on;
        proxy_read_timeout 180;
        send_timeout 180;

        client_max_body_size 64M;

        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme; # Use $http_x_forwarded_proto if NGINX is behind another trusted reverse proxy that sets X-Forwarded-Proto

        proxy_pass http://127.0.0.1:8894/;
    }
}

When Redropp is used behind a reverse proxy, make sure the proxy correctly sets the X-Forwarded-For and X-Forwarded-Proto headers.

You may need to change HTTP_TRUSTED_PROXIES (or TrustedProxies in the HTTP section of the configuration file) to include the address or network of your reverse proxy or proxies, as seen from inside the Docker container.

Redropp only uses forwarding headers such as X-Forwarded-For and X-Forwarded-Proto when they come from a proxy declared as trusted. This information is used, among other things, to mitigate certain attacks, for example by blocking repeated login attempts, and to strengthen cookie security.

Apache 2

Edit your Apache 2 config (directly or in a server file in /etc/apache2/sites-available) to make it work as a reverse proxy for Redropp.

The VirtualHost block should you something like this:

<VirtualHost *:443>
    # ...

    LimitRequestBody 67108864

    ProxyPreserveHost On
    ProxyAddHeaders On
    RequestHeader set "X-Forwarded-Proto" expr=%{REQUEST_SCHEME}

    ProxyPass "/" "http://127.0.0.1:8894/"
    ProxyPassReverse "/" "http://127.0.0.1:8894/"
</VirtualHost>

When Redropp is used behind a reverse proxy, make sure the proxy correctly sets the X-Forwarded-For and X-Forwarded-Proto headers.

You may need to change HTTP_TRUSTED_PROXIES (or TrustedProxies in the HTTP section of the configuration file) to include the address or network of your reverse proxy or proxies, as seen from inside the Docker container.

Redropp only uses forwarding headers such as X-Forwarded-For and X-Forwarded-Proto when they come from a proxy declared as trusted. This information is used, among other things, to mitigate certain attacks, for example by blocking repeated login attempts, and to strengthen cookie security.