this post was submitted on 16 Sep 2023
3 points (100.0% liked)
Pricefield.org Meta
113 readers
1 users here now
Suggestions, technical issues, complaints, anything concerning the instance
Welcome to the Pricefield corner of Lemmy! Here's a quick list of the communities you may find here:
> ♥ Pricefield ♥ <
> Life is Strange <
> LiS Franchise <
> Life is Silly <
(feel free to click, we made sure that the links will open on your own instance)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
i hate lemmy so much
finally figured out how to do it. i went through like 3-4 different ways until i managed to actually talk to pictrs for once, and of course the endpoint was different than in the public documentation because the thing on github only tracks it until 0.1.4 (while we run 0.4.0). plus i've never seen a file genuinely crash github (it always returned 500 on one of these, lol), and so on and on...
anyway, before i devolve into incoherent rambling about poorly documented and counterintuitive rust code, here's the command that worked for me:
if any instance admins are reading this, make sure you actually do have a pictrs api key set up. the right environment variable is
PICTRS__SERVER__API_KEY
, as opposed to thePICTRS__API_KEY
that comes in the docker-compose file (at least on 0.4.0, maybe this was different on an earlier version). that's probably why purging the post didn't work.anyway, the picture has been purged, and i sent out a cloudfront invalidation immediately after that's been confirmed, so it should be gone pretty much everywhere by now