Social embeds with oEmbed and Open Graph

[po5]

Differences with the approaches in #421, #422 and #441:

• No new dependencies (such as an extra server, Lua scripting module, Caddy)
• Proper Twitter meta tags (name attribute instead of property)
• Only serves dynamic HTML on pages we support embeds for (currently only posts but easily extensible)
• Returns 404 status code on deleted posts
• Very minimal implementation, easy to review
• Booru works just like it currently does for those who don't make the routing changes
• Implements both oEmbed and Open Graph for the very best compatibility

Things that can be improved later:

• Embedding of videos (currently shows a thumbnail)
• Caching (I personally don't think it's necessary, better to return up-to-date data and let the instance owner decide)
• Generic embed for static pages

Meant to be used with an nginx config like:

location ~ ^/booru/(post/[0-9]+)(?:/.*)?$ {
    set $query $1;
    proxy_pass http://127.0.0.1:6666/index/$query;
    proxy_set_header Accept "*/*";
}

Discord

Twitter

Closes #416

[ninjazan420]

May be a stupid question, but I have never changed something server side wise. So how could I implement it, after changing the files?
What I do for client side updates is docker compose down && docker compose build && docker compose up -d, but it doesn't catch the server updates :)

Thanks for your help!

[milezzz]

I merged this branch on a fresh git pull of rr-:master and I get 502 bad gateway errors. See screenshot.

The domain is behind cloudflare, if that matters. Any clue what could be causing this? Pulling my hair out :/

[TiredSysOp]

I merged this branch on a fresh git pull of rr-:master and I get 502 bad gateway errors. See screenshot.

The domain is behind cloudflare, if that matters. Any clue what could be causing this? Pulling my hair out :/

Post logs and check this https://github.com/rr-/szurubooru/wiki/Common-errors

[milezzz]

Well doesn't seem to be a permission issue. When I remove the embed merge and rebuild everything works again. Sorry here's the docker-compose logs output:

server-1  | INFO  [alembic.runtime.migration] Will assume transactional DDL.
server-1  | Starting szurubooru API on port 6666 - Running on 4 threads
server-1  | Traceback (most recent call last):
server-1  |   File "/usr/bin/waitress-serve-3", line 33, in <module>
server-1  |     sys.exit(load_entry_point('waitress==1.4.4', 'console_scripts', 'waitress-serve')())
server-1  |   File "/usr/lib/python3.8/site-packages/waitress/runner.py", line 270, in run
server-1  |     app = resolve(module, obj_name)
server-1  |   File "/usr/lib/python3.8/site-packages/waitress/runner.py", line 211, in resolve
server-1  |     obj = __import__(module_name, fromlist=segments[:1])
server-1  |   File "/opt/app/szurubooru/facade.py", line 11, in <module>
server-1  |     from szurubooru import api, config, db, errors, middleware, rest
server-1  |   File "/opt/app/szurubooru/api/__init__.py", line 2, in <module>
server-1  |     import szurubooru.api.embed_api
server-1  |   File "/opt/app/szurubooru/api/embed_api.py", line 13, in <module>
server-1  |     with open(f"{config.config['data_dir']}/../index.htm") as index:
server-1  | FileNotFoundError: [Errno 2] No such file or directory: '/data//../index.htm'```

[milezzz]

I took another stab at this but continue to get this error:

FileNotFoundError: [Errno 2] No such file or directory: '/data//../index.htm

I tried hardcoding the directory (/var/www/index.htm), but even that gets the same error which is confusing because I run:

sudo docker exec -it szurubooru-client-1 ls -al /var/www/

...and I confirm the index file is there. I assume it has something to do with the fact I am running inside a docker but not sure what's up. Pretty desperate to get some proper SEO built into my instance so if anyone has an idea how to get this working inside a docker I'd love to hear it.

[neobooru]

I believe this setup can't work for docker based deployments, because the index.htm file lives inside the client container and the server container wants to read it. I am not sure what the best solution to this would be.
Maybe the best solution would be 'true' server rendered pages? But that requires a lot of work. (E.g. rewriting client to use Nuxt or something like that).