Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/mimischi/minio-dokku
Dockerfile to run Minio (S3 compatible storage) on Dokku (mini-Heroku)
https://github.com/mimischi/minio-dokku
dokku minio
Last synced: about 2 months ago
JSON representation
Dockerfile to run Minio (S3 compatible storage) on Dokku (mini-Heroku)
- Host: GitHub
- URL: https://github.com/mimischi/minio-dokku
- Owner: mimischi
- Created: 2016-04-26T14:25:26.000Z (over 8 years ago)
- Default Branch: main
- Last Pushed: 2022-12-12T13:42:20.000Z (almost 2 years ago)
- Last Synced: 2024-07-28T13:14:17.155Z (about 2 months ago)
- Topics: dokku, minio
- Language: Dockerfile
- Size: 51.8 KB
- Stars: 133
- Watchers: 5
- Forks: 43
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
[]() []()
# Run Minio on Dokku
## Perquisites
### What is Minio?
Minio is an object storage server, and API compatible with Amazon S3 cloud
storage service. Read more at the [minio.io](https://www.minio.io/) website.
### What is Dokku?
[Dokku](http://dokku.viewdocs.io/dokku/) is the smallest PaaS implementation
you've ever seen - _Docker powered mini-Heroku_.
### Requirements
* A working [Dokku host](http://dokku.viewdocs.io/dokku/getting-started/installation/)
# Setup
We are going to use the domain `minio.example.com` and Dokku app `minio` for
demonstration purposes. Make sure to replace it.
## Create the app
Log onto your Dokku Host to create the Minio app:
```bash
dokku apps:create minio
```
## Configuration
### Setting environment variables
Minio uses two access keys (`ACCESS_KEY` and `SECRET_KEY`) for authentication
and object management. The following commands sets a random strings for each
access key.
```bash
dokku config:set --no-restart minio MINIO_ROOT_USER=$(echo `openssl rand -base64 45` | tr -d \=+ | cut -c 1-20)
dokku config:set --no-restart minio MINIO_ROOT_PASSWORD=$(echo `openssl rand -base64 45` | tr -d \=+ | cut -c 1-32)
```
To login in the browser or via API, you will need to supply both the
`ACCESS_KEY` and `SECRET_KEY`. You can retrieve these at any time while logged
in on your host running dokku via `dokku config minio`.
> **Note:** if you do not set these keys, Minio will generate them during
> startup and output them to the log (check if via `dokku logs minio`). You
> will still need to set them manually.
You'll also need to set other two environment variables:
- `NGINX_MAX_REQUEST_BODY`: used in the custom `nginx.conf` for this Dokku app
to allow uploads up to 15MB to the HTTP server (if the file size is greater
than 15MB, `s3cmd` will split in 15MB parts).
- `MINIO_DOMAIN`: used to tell Minio the domain name being used by the server.
```bash
dokku config:set --no-restart minio NGINX_MAX_REQUEST_BODY=15M
dokku config:set --no-restart minio MINIO_DOMAIN=minio.example.com
```
> **Note**: if you're using [s4cmd](https://github.com/bloomreach/s4cmd/)
> instead, be sure to pass the following parameters:
> `--multipart-split-size=15728640 --max-singlepart-upload-size=15728640`.
## Persistent storage
To persists uploaded data between restarts, we create a folder on the host
machine, add write permissions to the user defined in `Dockerfile` and tell
Dokku to mount it to the app container.
```bash
sudo mkdir -p /var/lib/dokku/data/storage/minio
sudo chown 32769:32769 /var/lib/dokku/data/storage/minio
dokku storage:mount minio /var/lib/dokku/data/storage/minio:/home/dokku/data
```
## Domain setup
To get the routing working, we need to apply a few settings. First we set
the domain.
```bash
dokku domains:set minio minio.example.com
```
The parent Dockerfile, provided by the [Minio
project](https://github.com/minio/minio), exposes port `9000` for web requests.
Dokku will set up this port for outside communication, as explained in [its
documentation](http://dokku.viewdocs.io/dokku/advanced-usage/proxy-management/#proxy-port-mapping).
Because we want Minio to be available on the default port `80` (or `443` for
SSL), we need to fiddle around with the proxy settings.
First add the correct port mapping for this project as defined in the parent
`Dockerfile`.
```bash
dokku proxy:ports-add minio http:80:9000
dokku proxy:ports-add minio https:443:9000
dokku proxy:ports-add minio https:9001:9001
```
Next remove the proxy mapping added by Dokku.
```bash
dokku proxy:ports-remove minio http:80:5000
```
## Push Minio to Dokku
### Grabbing the repository
First clone this repository onto your machine.
#### Via SSH
```bash
git clone [email protected]:slypix/minio-dokku.git
```
#### Via HTTPS
```bash
git clone https://github.com/slypix/minio-dokku.git
```
### Set up git remote
Now you need to set up your Dokku server as a remote.
```bash
git remote add dokku [email protected]:minio
```
### Push Minio
Now we can push Minio to Dokku (_before_ moving on to the [next
part](#domain-and-ssl-certificate)).
```bash
git push dokku master
```
## SSL certificate
Last but not least, we can go an grab the SSL certificate from [Let's
Encrypt](https://letsencrypt.org/).
You'll need [dokku-letsencrypt plugin](https://github.com/dokku/dokku-letsencrypt) installed. If it's not, install by running:
```bash
dokku plugin:install https://github.com/dokku/dokku-letsencrypt.git
```
Now get the SSL certificate:
```bash
dokku config:set --no-restart minio [email protected]
dokku letsencrypt:enable minio
dokku proxy:ports-set minio https:443:9000
```
> **Note**: you must execute these steps *after* pushing the app to Dokku
> host.
## Wrapping up
Your Minio instance should now be available on
[minio.example.com](https://minio.example.com).