minio

These are docker images for MinIO running on our Alpine Linux image.

For the available versions please look at Docker Hub or Quay or check the existing folders within the GitHub repository.

• /var/lib/minio

• 9000

MINIO_ADDRESS = 0.0.0.0:9000
MINIO_CONSOLE_ADDRESS = 0.0.0.0:9001
MINIO_HEALTHCHECK_CODE = 200
MINIO_HEALTHCHECK_URL = http://${MINIO_ADDRESS}/minio/health/live
MINIO_ROOT_PASSWORD = $(< /dev/urandom tr -dc _A-Za-z0-9+- | head -c40)
MINIO_ROOT_USER = $(< /dev/urandom tr -dc A-Z0-9 | head -c20)
MINIO_SKIP_CHOWN = false
MINIO_START_DIRECTORY = /var/lib/minio

Extracted by the command: grep -hE ': "\$\{(.*)\}"' latest/overlay/etc/entrypoint.d/*.sh | sed 's/: "\${//' | sed 's/:="/ = /' | sed 's/"}"$//' | sort | uniq

• webhippie/alpine

Generally we are following conventional commits when we apply changes. That way we are able to generate proper changelogs for every release. Please use always pull requests to integrate new functionalities or to fix issues.

For the release process we are following semantic versioning which clearly indicates if a new version just resolves bugs, includes new features or even includes breaking changes.

After installing the tools via mise install as described above set up the pre-commit hooks so they run automatically on every commit:

pre-commit install --hook-type pre-commit --hook-type commit-msg

pre-commit is managed by mise and will be available after mise install.

If you have changed something on the source you should simply commit following the mentioned conventions:

git checkout -b feat/new-feature
git add --all
git commit -m 'feat: added awesome new feature'
git push --set-upstream origin feat/new-feature

After pushing your changes into the Git repository you should create a pull request on GitHub. If the pull request have been merged and everything built fine it will also create automatically a new release at least once a week.

• Thomas Boerger

MIT

Copyright (c) 2015 Thomas Boerger <http://www.webhippie.de>