Nitish Tiwari nitisht

Run Minio Gateway Binary

Download this : https://cloud.google.com/sdk/downloads
Run the command and complete authentication for the first time

 gcloud init

If you are reauthenticating use this command instead

gcloud beta auth application-default login

Shared Backend Minio Quickstart Guide

Minio shared mode lets you use single NAS (like NFS, GlusterFS, and other distributed filesystems) as the storage backend for multiple Minio servers. Synchronization among Minio servers is taken care by design. Read more about the Minio shared mode design here.

Minio shared mode is developed to solve several real world use cases. Some of these are

You have already invested in NAS and would like to use Minio to add S3 co

Introducing Minio: Run your own S3 compatible cloud storage on Hyper.sh!

Storage has been long thought of as a complex, difficult to setup system. Even after the advent of quick deployment mechanisms like containers, problem somewhat persisted because of ephemeral nature of containers - it seemed counter-intuitive to store mission critical data on something that itself is supposed to be disposable.

Minio is an open source, S3 compatible, cloud-native object storage server, that makes storage as easy as launching a Docker container. On Hyper.sh, Minio servers are backed by Hyper.sh volumes that make sure, even if a container running Minio server goes down, the data is safe in the volume. As a true cloud-native application, Minio scales very well in a multi-tenant cloud environment.

Docker containers provide isolated environment for application execution, Hyper.sh enables effortless scaling by running multiple instances of these isolated applications. To scale Minio as per your s

Introducing Minio: Run your own S3 compatible cloud storage on Hyper.sh!

Storage has been long thought of as a complex, difficult to setup system. Even after the advent of quick deployment mechanisms like containers, problem somewhat persisted because of ephemeral nature of containers - it seemed counter-intuitive to store mission critical data on something that itself is supposed to be disposable.

Minio is an open source, S3 compatible, cloud-native object storage server, that makes storage as easy as launching a Docker container. On Hyper.sh, Minio servers are backed by Hyper.sh volumes that make sure, even if a container running Minio server goes down, the data is safe in the volume. As a true cloud-native application, Minio scales very well in a multi-tenant cloud environment.

Docker containers provide isolated environment for application execution, Hyper.sh enables effortless scaling by running multiple instances of these isolated applications. To scale Minio as per your s

Pre-Conditions: https://docs.docker.com/engine/swarm/swarm-tutorial/#/three-networked-host-machines For distributed Minio to run, you need 4 networked host machines.
Create a new swarm and set the manager. SSH to one of the host machine, which you want to set as manager and run: docker swarm init --advertise-addr <MANAGER-IP>
Current node should become the manager. Check using: docker node ls
Open a terminal and ssh into the machine where you want to run a worker node.
Run the command as output by the step where master is created. It will add the current machine (as a worker) to the swarm. Add all the workers similarly.
Check if all the machines are added as workers, SSH to the master and run: docker node ls

Create an overlay network:

Features of Minio Server.

Item	Specification
Custom access key	environment MINIO_ACCESS_KEY
Custom secret key	environment MINIO_SECRET_KEY
Turn off web browser	environment MINIO_BROWSER=off
Listening on bucket notifications	using an extended S3 API
Support for bucket notifications	postgres, amqp, nats, elasticsearch, redis, kafka (in-progress)
Shared Backend (FS)	In-progress

	apiVersion: extensions/v1beta1
	kind: Deployment
	metadata:
	# This name uniquely identifies the Deployment
	name: minio-deployment
	spec:
	strategy:
	type: Recreate
	template:
	metadata:

	apiVersion: v1
	kind: Service
	metadata:
	name: minio
	labels:
	app: minio
	spec:
	clusterIP: None
	ports:
	- port: 9000

	apiVersion: v1
	kind: Service
	metadata:
	name: minio-endpoint
	spec:
	selector:
	app: minio
	ports:
	- name: "s3"
	port: 9000

	apiVersion: v1
	kind: Service
	metadata:
	name: minio-server
	labels:
	app: minio
	spec:
	ports:
	- port: 9000
	targetPort: 9000