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.
Cool, you are probably the first person other than us devs to run an instance :)
For image uploads, I am working on a solution here but am stuck with it. Alternatively you can change your traefik config based on the nginx config, so that requests to /pictshare are forwarded to http://0.0.0.0:8537/. That should be easy if you know how traefik config works (I dont).
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?
Cool! I dont understand how it uses https seeing as you put port 80, but I guess thats handled by the traefik config. Do you want to open a PR with this?
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?
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.
Cool, you are probably the first person other than us devs to run an instance :)
For image uploads, I am working on a solution here but am stuck with it. Alternatively you can change your traefik config based on the nginx config, so that requests to /pictshare are forwarded to http://0.0.0.0:8537/. That should be easy if you know how traefik config works (I dont).
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?
The frontend sends those requests to
:443/pictshare, and on the server those requests are forwarded to the other Docker container on port 8537.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"Cool! I dont understand how it uses https seeing as you put port 80, but I guess thats handled by the traefik config. Do you want to open a PR with this?
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?
Hmm not sure whats the best place to put it. ping /u/dessalines
It’d be good to put in the repo somewhere, maybe in
docker/prodfolder.There was a .onion instance but sadly whoever started it took it down about a month ago. It used to be: lemmyzojrcyxoqud.onion Their old reddit post: https://www.reddit.com/r/onions/comments/ed9jj7/lemmyzojrcyxoqudonion_a_lemmy_instance_for_the/