Thomas Biesaart

Hm, I was thinking about requirements and I might actually be changing my opinion. Since this is related to the build artifacts it might be more logical to do thing...

I just tested with my Pro v3 and when I connect it wireless (1532:025C) it is an unrecognized device. But through USB (1532:025A) it works fine. Environment info: ``` $...

@atombombzero probably not as #1623 is still open

We (very) briefly discussed this in Discord: https://discord.com/channels/725371605378924594/1145983898644389908/1217565350594609213

> Are you rebuilding the bundle extension after changes? I dont see that crucial step in the reproduction steps. Yes, fair enough. My extension is running in watch mode. And...

No idea if it helps but I just removed all records from `directus_extensions` and restarted directus. That was sufficient to trigger a rescan.

If you can just give me a pointer, then I can create a pull request as well. No problem.

I think I may have figured something out: I couldn't curl from the Lemmy container. Turned out I had no internet connection. Well makes sense because the default docker setup...

What I did is remove the network separation: ``` version: "3.3" services: proxy: image: nginx:1-alpine ports: # only ports facing any connection from outside - 80:80 - 443:443 volumes: -...

@andrewgioia try this nginx.conf: ``` events { worker_connections 1024; } http { upstream lemmy { # this needs to map to the lemmy (server) docker service hostname server "lemmy:8536"; }...