[-] ohai@subsubd.com 2 points 1 year ago* (last edited 1 year ago)

yeah, I just spent the last hour writing some python to grab all the mappings via the pict-rs api. Didn't help that the env var for the pictrs api token was named incorrectly (I should probably make a PR to the Lemmy ansible repo). EDIT: Nevermind, seems there is one already! https://github.com/LemmyNet/lemmy-ansible/pull/153

[-] ohai@subsubd.com 3 points 1 year ago

This is absolutely amazing!

[-] ohai@subsubd.com 3 points 1 year ago

Encino Man!

[-] ohai@subsubd.com 3 points 1 year ago

I'm writing a frontend in flask right now and something like this would be a godsend. Trying to dig not just the endpoints out of the lemmy/lemmy-ui/lemmy-js-client but also figuring out responses forenough variations has been like pulling teeth. Only thing more helpful would be an openapi spec.

[-] ohai@subsubd.com 1 points 1 year ago

I'll be in the cold, cold ground before I recognize Missourah!

[-] ohai@subsubd.com 4 points 1 year ago

Even better from the right one!

[-] ohai@subsubd.com 8 points 1 year ago

that's fair, just force of habit, i guess. thanks for the heads up! :)

[-] ohai@subsubd.com 16 points 1 year ago

docker compose down && docker compose pull && docker compose up -d update was flawless. nice!

ohai

joined 1 year ago