Webreaper / Damselfly

Damselfly is a server-based Photograph Management app. The goal of Damselfly is to index an extremely large collection of images, and allow easy search and retrieval of those images, using metadata such as the IPTC keyword tags, as well as the folder and file names. Damselfly includes support for object/face detection.
GNU General Public License v3.0
1.45k stars 76 forks source link

Unable to change Damselfly's port #534

Closed Badwolf369 closed 2 months ago

Badwolf369 commented 2 months ago

My compose file is set up like so:

services:
  damselfly-dev:
    container_name: damselfly-dev
    image: webreaper/damselfly
    ports:
      - 8081:81/tcp
    volumes:
      - S:/media-server/dev-photos-damselfly/services/damselfly:/config
      - S:/media-server/dev-photos-damselfly/services/damselfly/thumbs:/thumbs
      - S:/media-server/dev-photos-damselfly/library:/pictures
    restart: unless-stopped

This is the dev instance which runs on port 8081. This is so experimental config changes dont affect the main instance on port 6363. However, navigating to localhost:8081 gets an ERR_EMPTY_RESPONSE. Also, with Damselfly running on port 8081 only, navigating to localhost:6363 displays the damselfly loading page, but it never loads. When running one instance on 8081 and one on 6363, the instance on 6363 works as expected.

Webreaper commented 2 months ago

Damselfly runs on port 6363. So you need to map the internal container port of 6363 to the external container port of 8081 if you want to run your dev instance so that people can access it using 8081. So you probably want:

  ports:
      - 8081:6363

That's how I do it. (I use 6362 for my 'beta' instance, but 8081 should work just as well).

Badwolf369 commented 2 months ago

That worked! Thanks!