#Setting with Compose install

1 messages · Page 1 of 1 (latest)

lean nimbus
#

Hello,

I am trying to get Ente to run and it has raised a few questions

Can you guys help?

  1. Is Minio come installed with it, or do I need to install it sep? Ente web app seems to be running on the sever, if that helps

  2. How do I set up the api endpoint using a reverse api? I tried to link it to enteapi.mydomain.com. Also, ports 8080, and 443 are already in use.

My firewall blocks all ports except 80, and 443, so I have set up a reverse proxy as follows:

<virtualHost *:80>
ServerName enteapi.mydomain.com
ProxyPass / http://localhost:3200/
ProxyPassReverse / http://localhost:3200/
</virtualHost>

<virtualHost *:80>
ServerName ente.mydomain.com
ProxyPass / http://localhost:8081/
ProxyPassReverse / http://localhost:8081/
</virtualHost>

The webapp runs, but doesn’t accept enteapi.myentedomain.com as my api_endpoint. Does that need to be set elsewhere?

  1. I attached the compose.yaml file, I think this is set up correctly, but I’m not sure
verbal shoalBOT
#

Remember to use </solved:1383817028372135986> to mark your thread as solved once your question is answered.

tepid igloo
#

Mino is installed but I had to do additional setup
(You can see if its running with docker ps)

#

Are you using nginx?

little canopy
lean nimbus
lean nimbus
lean nimbus
# little canopy Yes

I changed the following:

    image: ghcr.io/ente-io/web
    # Uncomment what you need to tweak.
    ports:
      - 3000:3000 # Photos web app
      # - 3001:3001 # Accounts
      - 3002:3002 # Public albums
      # - 3003:3003 # Auth
      # - 3004:3004 # Cast
    # Modify these values to your custom subdomains, if using any
    environment:
      ENTE_API_ORIGIN: https://localhost:8081/
      ENTE_ALBUMS_ORIGIN: https://localhost:3002
    image: ghcr.io/ente-io/web
    # Uncomment what you need to tweak.
    ports:
      - 3000:3000 # Photos web app
      # - 3001:3001 # Accounts
      - 3002:3002 # Public albums
      # - 3003:3003 # Auth
      # - 3004:3004 # Cast
    # Modify these values to your custom subdomains, if using any
    environment:
      ENTE_API_ORIGIN: https://enteapi.mydomain.com:8081/
      ENTE_ALBUMS_ORIGIN: https://localhost:3002

didn't seem to make a difference.

If I load the endpoint in my browser, should I see anything? At the moment I just get a "service unavailable" screen. I assumed that was because the endpoint didn't send anything the browser could use

little canopy
lean nimbus
little canopy
lean nimbus
#

Excellent,

I set that and it's still giving me errors.

Can I ask, if i load up the API url in a browser, what should I see?

Also, minio works on port 3200, which is blocked by the firewall, but I am assuming that only called from withinthe localhost, so it shouldn't matter. correct?

lean nimbus
# little canopy API is running in 8080 in container. So you will have to use 8081:8080

Here is my compose.yaml

  museum:
    image: ghcr.io/ente-io/server
    ports:
      - 8081:8080 # API
    depends_on:
      postgres:
        condition: service_healthy
    volumes:
      - ./museum.yaml:/museum.yaml:ro
      - ./data:/data:ro

  # Resolve "localhost:3200" in the museum container to the minio container.
  socat:
    image: alpine/socat
    network_mode: service:museum
    depends_on: [museum]
    command: "TCP-LISTEN:3200,fork,reuseaddr TCP:minio:3200"

  web:
    image: ghcr.io/ente-io/web
    # Uncomment what you need to tweak.
    ports:
      - 3000:3000 # Photos web app
      # - 3001:3001 # Accounts
      - 3002:3002 # Public albums
      # - 3003:3003 # Auth
      # - 3004:3004 # Cast
    # Modify these values to your custom subdomains, if using any
    environment:
      ENTE_API_ORIGIN: http://enteapi.mydomain.com
      ENTE_ALBUMS_ORIGIN: https://localhost:3002

  postgres:
    image: postgres:15
    environment:
      POSTGRES_USER: pguser
      POSTGRES_PASSWORD: EDITED OUT
      POSTGRES_DB: ente_db
    healthcheck:
      test: pg_isready -q -d ente_db -U pguser
      start_period: 40s
      start_interval: 1s
    volumes:
      - postgres-data:/var/lib/postgresql/data

  minio:
    image: minio/minio
    ports:
      - 3200:3200 # MinIO API
      # Uncomment to enable MinIO Web UI      
      # - 3201:3201
    environment:
      MINIO_ROOT_USER: EDITED OUT
      MINIO_ROOT_PASSWORD: EDITED OUT
    command: server /data --address ":3200" --console-address ":3201"
    volumes:
      - minio-data:/data
    post_start:
      - command: |
          sh -c '
          #!/bin/sh

          while ! mc alias set h0 http://minio:3200 minio-user-EDITED OUT 2>/dev/null
          do
            echo "Waiting for minio..."
            sleep 0.5
          done

          cd /data

          mc mb -p b2-eu-cen
          mc mb -p wasabi-eu-central-2-v3
          mc mb -p scw-eu-fr-v3
          '
volumes:
  postgres-data:
  minio-data:
little canopy
#

Lgtm. Isn't domain for API https? Check that once.

lean nimbus
#

I did try it a few times with and without https. I will check it again.

Do you know what happens when you load the api url directly into a browser?

little canopy
lean nimbus
lean nimbus
# little canopy Try checking this: https://enteapi.mydomain.com/ping

I turned off the other applicaton that was using 8080, and then I changed everything on ente back to the default ports,

I then went into terminal and did ping https://localhost:8080 and it said it could not connect.

I don't think this is a port or a firewall issue, I think the api simply isn't running.

I say this because it would connect using that command with the other application

little canopy
lean nimbus
little canopy
#

Build I think isn't needed. Doing a down could have worked. Interesting. Thanks for letting us know about this :)

verbal shoalBOT
#

Thread marked as solved. It will be closed in <t:1752726828:R>.