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

question: Alternative tool for minio #1730

Closed
nelajc opened this issue Apr 24, 2024 · 4 comments
Closed

question: Alternative tool for minio #1730

nelajc opened this issue Apr 24, 2024 · 4 comments
Labels
question Further information is requested

Comments

@nelajc
Copy link

nelajc commented Apr 24, 2024

is there any tool or service we can use to replace minio for this apitable stack?

@nelajc nelajc added the question Further information is requested label Apr 24, 2024
@ChambersChan
Copy link
Collaborator

Services compatible with S3 SDK can modify the environment variable(L107 - L110) value accordingly.

@nelajc
Copy link
Author

nelajc commented May 21, 2024

thanks. but how can i tell if s3 is connected properly to apitable stack?

also. should i stop/remove the minio container right?

@nelajc
Copy link
Author

nelajc commented May 22, 2024

Services compatible with S3 SDK can modify the environment variable(L107 - L110) value accordingly.

seems this one not working.. upstream and imageproxy configs of gateway container is searching for minio..

@ChambersChan
Copy link
Collaborator

Services compatible with S3 SDK can modify the environment variable(L107 - L110) value accordingly.

seems this one not working.. upstream and imageproxy configs of gateway container is searching for minio..

Sorry. I missed the env configuration inside the service (ASSETS_URL、OSS_HOST and QNY1).
They can be assigned to s3 or cdn addresses, for example, using local minio to assign 'http://127.0.0.1:9000/'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants