-
-
Notifications
You must be signed in to change notification settings - Fork 160
Add MinIO Docker Compose Service #173
base: master
Are you sure you want to change the base?
Conversation
Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much for this contribution! @truls1502 was also working on this at some point, so requesting his review here.
I wasn't able to get this working, from the host browser the http URL says:
$ curl http://d9.ddev.site:9000
<html>
<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>The plain HTTP request was sent to HTTPS port</center>
<hr><center>nginx/1.20.1</center>
</body>
</html>
And the https port gets a 400 error:
$ curl https://d9.ddev.site:9000
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied.</Message><Resource>/</Resource><RequestId>16BF76401B7CA5EB</RequestId><HostId>e3483c39-1c6f-4b72-bcbc-5fe39a3bac71</HostId></Error>
I imagine that's just because I don't know how to provide credentials?
The server is configured through the environment variables in `docker-compose.minio.yaml` | ||
Default credentials (for API and object browser): | ||
* MINIO_ACCESS_KEY=minio | ||
* MINIO_SECRET_KEY=minio123 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if these would be better to put in config.yaml these days, rather than having people edit the docker-compose.minio.yaml.
* Start (or restart) DDEV to have the service initialized: `ddev start` | ||
|
||
## Connection | ||
* MinIO is available at `ddev-<projectname>-minio:9000` **inside the containers** and at `https://<projectname>.ddev.site:9000` **outside the containers** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please figure out how to move this to a port other than 9000. 9000 is always such a terrible thing, spurring fights between xdebug and php-fpm... and even minio!!!!
build: | ||
context: './minio-build' | ||
restart: always | ||
ports: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use expose:
here instead of ports:
. That will make it not create a bind point on the host, which is unneeded.
ports: | |
expose: |
Looking forward to getting this in @NBZ4live and thanks for the contribution. Please just pull the suggested commits and rebase and respond to other comments and we can move forward. |
Tried following the steps but unfortunately doesn't seem to be working. Do you know if this should work with the m1 chips? |
https://drupal9-ddev.ddev.site:9000/ redirects to http://drupal9-ddev.ddev.site:39085/ and throws a connection refused error When I change the port from 9000 to 9005 and try to visit the url I get 502: Unresponsive/broken ddev back-end site. |
Okay finally got it working `version: '3.6' volumes: |
@mglaman points out that he has minio going on https://github.com/bluehorndigital/mojo |
Hi @rfay any info on this? I was hoping to have a service as well for local development. if I use this file
there are issues in starting up the project. Is there any specific thing that I need to adjust in here? |
@zaifastafa please say what the issues are, and maybe somebody can help you. It would be great if somebody who uses this would turn it into a ddev add-on. |
When this file is added and I do ddev restart, the project starts fine but when opening the project it gives 503 ddev error. |
A 503 normally means you have the wrong docroot or that the docroot has no index.php in it. Please do a standard trivial working project, maybe Drupal9 quickstart or something, and add this, and see if you still have the problem. |
Hello, I've implemented a full DDEV MinIO addon here. https://github.com/oblakstudio/ddev-minio Fully tested and it works |
FWIW, I have been using @seebeen's ddev-minio and it is working great. |
@rfay can we move the ddev-minio to the official namespace? |
Sure, please open an issue in ddev-minio. I'm in Chile, it may be a while but we'll do it. |
The New Solution/Problem/Issue/Bug:
This recipe adds a MinIO container to a project.
MinIO is a S3 compatible object-storage.
It can be used, to run an S3 instance locally, in case the hosted S3 is not reachable (like developing while offline)
Manual Testing Instructions:
Follow the instructions from
docker-compose-services/minio/README.md
.Expected result:
https://<projectname>.ddev.site:9000
.ddev exec -s minio ls -al /data/default