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
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.
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
This is absolutely amazing!
Encino Man!
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.
I'll be in the cold, cold ground before I recognize Missourah!
Even better from the right one!
that's fair, just force of habit, i guess. thanks for the heads up! :)
docker compose down && docker compose pull && docker compose up -dupdate was flawless. nice!