- changed all service names to not include "forget", let docker-compose
generate container names
- gave the image a single name
- listen on 127.0.0.1 by default, provide documented override file that
reverses it
- docs: on that note: don't tell folks to edit docker-compose.yml directly
- docs: explicitly say "run docker-compose build" because docker-compose
is janky and it can be surprising that downloading a new version of
the code and running `docker-compose up` doesn't do anything
also lock some versions
ideally I wouldn't have to copy each of these directories separately and
have a janky stage to hide all the resulting layers, but docker do be like that.
`COPY dir1 dir2 ./` copies *the contents of* dir1 and dir2 to the
working directory :(
maybe one day i will switch to having a src directory
it's been over three years since the old forget_known_instances cookie
is no longer being set, any cookie that hasn't been upgraded to
localstorage by now has surely expired
This implementation does not actually read favourites, but reactions,
because reading favourites is more involved as they are like bookmarks
on Mastodon and not attached to the post itself.
Also removing the respective erroneous authentication scope.
Instead of using Query.one use Query.one_or_none. The check after
setting the variable suggests this was the intended behaviour instead
of throwing errors if there are no posts in the database.
codl
shibao
Johann150