My wife and I ordered a pizza and binged on Pennyworth.

Sounds good. I’ve created an issue for tracking it on github, I’ll submit a PR.

Slight typo on my end there - the port refers to the back end docker container, so it’s 8536 for lemmy, 80 for pictshare.

I’d be happy to open a PR for it, but without existing config for either nginx or traefik in the standard docker-compose, I wonder if it would be better just to be included in the documentation somewhere?

Moderation issues aren’t usually a concern for the person making the post, they tend to crop up a few hours later when the arguments start - by which point the ship has already sailed. From a technical standpoint, how such a post would be moderated is something that would need careful consideration.

I’ve now got it working. For reference, below is my docker-compose with the traefik labels for each:

  lemmy:
    image: dessalines/lemmy:v0.6.17
    container_name: lemmy
    volumes:
      - ./lemmy.hjson:/config/config.hjson:ro
    labels:
      - "traefik.enable=true"
      - "traefik.frontend.rule=Host:gix.uk"
      - "traefik.port=8536"
  pictshare:
    image: hascheksolutions/pictshare:latest
    container_name: pictshare
    volumes:
      - /data/pictshare/data:/usr/share/nginx/html/data
    labels:
      - "traefik.enable=true"
      - "traefik.api.frontend.rule=Host:gix.uk;PathPrefixStrip:/pictshare"
      - "traefik.port=80"

Moderation would be the main challenge. If the same content is posted to multiple communities with opposing viewpoints, it would likely become a wasteland due to moderator infighting.

I’m looking at a couple of options, either using traefik configuration directly or adding in an nginx container to handle the path based routing and leaving traefik to just deal with SSL.

Where does the image upload feature try to get to - port 8537 or /pictshare?

I just started an instance a few days ago (gix.uk). There’s nothing there right now, and I’m not sure exactly what, if anything, I’ll do with it. I figure I’ll probably keep it going at least until federation goes live, and make a decision based on whether or not there’s actually any content there by that point, and whether enabling federation causes any loss of local content, or just makes it available to other instances in the same way that Peertube etc does.

Unfortunately, image upload doesn’t work right now because I use traefik rather than nginx as a reverse proxy. I may try to fix it and possibly submit a PR for it, but I suspect it’s not going to be a simple job and could well be beyond my abilities.