Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc(quickstart): use local minIO instead of remote minIO service #450

Closed
seeflood opened this issue Apr 7, 2022 · 2 comments · Fixed by #464
Closed

doc(quickstart): use local minIO instead of remote minIO service #450

seeflood opened this issue Apr 7, 2022 · 2 comments · Fixed by #464
Assignees
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers help wanted Extra attention is needed

Comments

@seeflood
Copy link
Member

seeflood commented Apr 7, 2022

What would you like to be added:
Change MinIO's demo to:

  • use docker to deploy MinIO by default
  • Layotto invoke local MinIO by default

Why is this needed:
Currently, the demo uses the MinIO official demo service by default, but the service is unstable.
image

For example , someone might modify some configuration, which leads to demo failure.
So we want to use docker to deploy MinIO and make the demo more stable.

@seeflood seeflood added documentation Improvements or additions to documentation good first issue Good for newcomers help wanted Extra attention is needed labels Apr 7, 2022
@ZLBer
Copy link
Member

ZLBer commented Apr 7, 2022

/assign

@seeflood
Copy link
Member Author

seeflood commented Apr 8, 2022

@ZLBer Thanks!
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants