You are browsing as a guest. Sign up (or log in) to start making projects!

immich AUR package

  • 4 Devlogs
  • 3 Total hours

so, immich is this magnificent backup service you can host on ye compoote. Because of its great amount of dependencies, upstream recommends sealing it off in a docker glasshouse. But that's preposterous! For at least on my Arch BTW installation, running docker breaks my Waydroid Internet! Thus for this and other reasons to dislike the proprietary blåhaj, we AUR idiots pulled it out of container safehaven to run on bare metal—interfacing with our actual machine's libraries!

Open comments for this post

55m 46s logged

Oof, the reviewer used an AUR helper that hid the post-install instructions among a deluge of messages! Ze had a point that I should have those instructions in the reviewer-only README too, I’ll admit. I’ve spent the last thirty minutes doing that.

No, that is not what I did within the logged time. A very helpful user commented on the AUR page that I had an issue stemming from the redis→valkey migration last year. I was adding us to the redis user group while depending on valkey!
Remembering my sympathy for the redis founder’s account of the events, I decided to fix this by supporting both, by adding to both the redis and valkey groups and depending on “redis”, which valkey also provides.
(What does that mean? Arch’s pacman has a nifty feature—provides—so that valkey can label itself as providing all the features of the redis package, which it does. Well, almost, minus the user-group name change, anyways.)

The reviewer also exposed a problem in the immich-admin script when ze mistakely tried to launch immich with it. Firstly, I neglected to mention that the script probably shouldn’t be used, as the systemd service wraps around it—a service I didn’t mention either. 🥀. Secondly, it now fails when not called from its working directory. I’ve fixed this by replacing the symlink with a short script that first cd-s to the correct directory, and of course adding that to the README.
Finally, I’ve updated the nginx config to the proper format (with an events {} section) and dropped migration instructions for too-old versions, as promised in the document containing migration instructions. Past 9 months mean you get sent off from the womb into the wild before you are replaced with our best instructions yet we are so proud to present you with at this year’s worldwide instruction conferen


A yay for interchangeable parts. That’s right, use yay or paru instead. Interchange those blasted bloasted TUIs. Start a revolution. /hj

0
0
2
Open comments for this post

38m 42s logged

I swear I saw “immich-core-plugin”. Turns out it was corePlugin→immich-plugin-core. Oops.

Edit: The last reviewer ignored the link to the README and said there was not README present in the source code link. Unfortunately AUR’s nature makes it bad for me to have a README in the branch where the source code is, so now the source code is under the master branch.

0
0
1
Ship #1 Pending review

update after 10 minutes: it was ridiculously simple! the relevant env follows the same format as `PATH`. i've followed the Dockerfile's footsteps in cancelling the Flutter download, and now everything works as well as it has before.

AUR users can now enjoy immich's new Workflows feature and more.

to test this project, make sure you use Arch, don't have any irregularities under /usr/ (if you never used things that aren't pacman or AUR helpers to modify this directory, you should be fine), and install the `immich-server` AUR package

  • 2 devlogs
  • 1h
Try project → See source code →
Open comments for this post

20m logged

at first downloads were failing because Steam was downloading shader cache updates for Train Sim World, dangit.

obviously it turned out I had more to do. i forgot to adapt all of the changed paths: cli/→packages/cli/, plugins/→packages/plugin-core/, and corePlugin→plugins/immich-core-plugin (ooh they released plugins!). i also discovered that the build was in fact not reproducible just by adding build ID as we do timestamp the geodata, so let’s incorporate that. now i have to deal with the updates to mise configuration

0
0
2
Open comments for this post

49m 48s logged

first step is obvious: check the list of changes to server/Dockerfile. that specifies the recipe to create the Docker image—essentially packaging instructions that’ve already been written for us. it wasn’t much, thankfully (unlike the RapidOCR changes…): they separated out an additional plugin SDK we’d need to build and now explicitly build the dependent SDKs first.
the migration to pnpm 11 also meant --frozen-lockfile needs to be passed to the install command, so i took this opportunity to put such relevant flags after the subcommand portion of the command as well. finally let’s clarify the pkgdesc cuz why not

0
0
29

Delete project?

Are you sure you want to permanently delete this project? This action cannot be undone.

All devlogs, followers, and associated data will be removed.

Followers

Loading…