heblo duelists today i have a release of many little things for you. not much flashy today, it’s mostly much-needed fixes and other such fun and games
i do have a fun one though!
New stuff
Image metadata now prefills descriptions
The ExifTool.ReadDescription upload filter has been added! When activated, this will utilise Exiftool to read image metadata and attempt to prefill the description field. Useful
Please note that if also using ExifTool.StripMetadata, the ordering is important! We can’t read metadata that we’ve already stripped, after all. So ReadDescription has to come before StripMetadata
There is one database migration this month, so don’t forget to run your ecto.migrate on source or migrate on OTP!
Thankies
Oneric for many fixes and practically being a co-maintainer these days. wooo Norm for documentation fixes!
timorl and ilja for the exiftool rework and new upload filter! erincandescent for compatibility fixes on the AP level!
Helge for fep compliance work! Snan for .atom display fixes!
i was a little late on the admin-fe builds so if you notice that you don’t have StripMetadata config options in the admin-fe, you updated before the release went out, my apologies~
Thank you very much for your work with Akkoma. I just tried the upgrade and ran into the error below:
sudo ./docker-resources/manage.sh mix compile
[+] Creating 1/0
✔ Container akkoma-db Running 0.0s
Compiling 333 files (.ex)
Compiling lib/pleroma/web/gettext.ex (it's taking more than 10s)
error: module Pleroma.Web.ActivityPub.Visibility is not loaded and could not be found. This may be happening because the module you are trying to load directly or indirectly depends on the current module
lib/pleroma/web/mastodon_api/views/status_view.ex:26: Pleroma.Web.MastodonAPI.StatusView (module)
== Compilation error in file lib/pleroma/web/mastodon_api/views/status_view.ex ==
** (CompileError) lib/pleroma/web/mastodon_api/views/status_view.ex: cannot compile module Pleroma.Web.MastodonAPI.StatusView (errors have been logged)
are you on a clean git checkout? since it compiles elsewhere without issue, i can only imagine that you’ve made local changes and run into merge issues
Right. For the first time in a very long time, the update didn’t go smoothly. Now my instance is doing a 502 no matter what I’m doing. I literally followed the instructions for OTP install upgrade, as I have done multiple times before. Trying to work out if I have missed a step in the instructions in here, but if I have, I can’t see it.
The instance (Ubuntu 22.04) has been running for over a year and I usually keep on track with latest release for everything. I do have the config in the database. Would I perhaps need to add something to the config file still? Perhaps it is loaded before the database config kicks in?
The commands I’ve run, as instructed on the upgrade page:
It’s ok, I think I had what @Kris had: somehow we got through the previous update without updating the config file. I didn’t update it at the time as I wasn’t sure if I needed to (as I have the config in the database).
Now, as things weren’t working and I saw that Kris got his stuff to run after adding it, I did too, thinking I had nothing to lose. Turns out it is a good thing indeed, and now my instance is up again.
When I did the last update I had to add "config :pleroma, Pleroma.Upload, base_url: “https://example.com/media/” like Kris. That’s still in place so I’m not sure what to look at next. Any suggestions would be appreciated.
just… as a general rule of thumb always check your logs
we here at akkoma gang incorporated plc GmbH LLC do not install backdoors on your machine and hence we do actually require you to do some basic information gathering before requesting assistance
One of the things which keeps on confusing me is the nomenclature of Akkoma.
Here we are talking about release 2024.04.1 and the likes, but in the app all I see is Backend version 3.13.2?
Do the version numbers and backend version relate in any way?
I can check the local Changelog.md, but that will only tell me that this file was updated not necessarily what “binary” I am running.
I see. And because the UIs aren’t controlled by you, the UIs don’t know about your version and pull up the Elixier version.
The consequence is that it’s impossible for a user to determine if his server is running the latest software, and an admin will have to ssh into the Akkoma install directory to check the CHANGELOG file in case he didn’t closely follow your releases.
Anyway, given my two small instances this is a rhetorical conversation rather than a problem for me, and I will happily go with what works best for you.
