Why not use the default MinIO FTP server to optimize resources?

[AissaGeek]

``Hi,
I noticed that the current setup uses a separate STP server and a Python watcher to push objects to MinIO. Could you please clarify why this approach was chosen instead of using the default MinIO FTP server? Utilizing the default MinIO FTP server could potentially decrease resource usage and simplify the architecture. Are there specific benefits or requirements that led to the current configuration?

something like that :

  minio:
    image: minio/minio:RELEASE.2024-02-13T15-35-11Z
    environment:
      MINIO_FTP_EXTERNAL_IP: ""
      MINIO_FTP_PORT: "8021"
      MINIO_FTP_PASV_RANGE: "30100-30110"
    entrypoint: /entrypoint.sh
    ports:
      - "9090:9000"
      - "9091:9001"
      - "8021:8021"
      - "30100-30110:30100-30110"
    env_file:
      - ./assets/minio/.env.minio
    volumes:
      # TODO bind to host /data
      - minio_data:/data
      - ./assets/minio/config/config.json:/root/.minio/config.json:ro
      - ./assets/minio/entrypoint.sh:/entrypoint.sh:ro
    networks:
      - ibf-network

  createbuckets:
    image: minio/mc:RELEASE.2024-03-30T15-29-52Z.fips
    deploy:
      replicas: 1
      restart_policy:
        condition: on-failure
        delay: 5s
        max_attempts: 3
    env_file:
      - ./assets/minio/.env.minio
    volumes:
      - ./assets/minio/init_minio.sh:/scripts/init_minio.sh
      - ./assets/minio/config/lifecycle_deletion.json.template:/scripts/lifecycle_deletion.json.template:ro
    depends_on:
      - minio
    entrypoint: /bin/bash /scripts/init_minio.sh
    networks:
      - ibf-network