Package Details: photoprism 251130-1

Git Clone URL: https://aur.archlinux.org/photoprism.git (read-only, click to copy)
Package Base: photoprism
Description: AI-Powered Photos App for the Decentralized Web
Upstream URL: https://github.com/photoprism/photoprism
Keywords: ai cloud golang photography
Licenses: AGPL-3.0-or-later
Conflicts: photoprism-facenet, photoprism-nasnet, photoprism-nsfw
Replaces: photoprism-facenet, photoprism-nasnet, photoprism-nsfw
Submitter: evine
Maintainer: shtrophic
Last Packager: shtrophic
Votes: 3
Popularity: 0.125518
First Submitted: 2024-06-18 05:57 (UTC)
Last Updated: 2025-12-02 20:08 (UTC)

Dependencies (15)

Required by (0)

Sources (13)

Pinned Comments

shtrophic commented on 2025-04-25 14:03 (UTC) (edited on 2025-04-25 14:04 (UTC) by shtrophic)

Please note: since upstream switched to tensorflow-2.x, there is no need anymore to vendor a compatible tensorflow version as the photoprism-tensorflow-* packages.

I also chose to vendor the model weights again, to simplify everything. (effectively un-doing the efforts of the previous maintainer, who chose to create a new package for every zip/tarball. It is definitely an opinionated change, but it should have no effect on end-users).

Therefore, this package now depends on tensorflow (which can be either -opt,-cuda and so on) and conflicts/replaces phoroprism-{nasnet,nsfw,facenet}.

evine commented on 2024-09-04 01:58 (UTC) (edited on 2024-09-24 04:22 (UTC) by evine)

Do not use nodejs 22.7.0/22.8.0 to make.

Latest Comments

1 2 Next › Last »

deepsea22 commented on 2025-12-04 09:22 (UTC)

@shtrophic Thank you! I didn't realize I needed to manually replace the config. It all works after removing the diff, specifically: 1a2

ModelsPath: /usr/share/photoprism 5a7 VisionYaml: /var/lib/photoprism/config/vision.yml

shtrophic commented on 2025-12-04 07:28 (UTC)

@deepsea22 please diff /etc/photoprism/defaults.yml{,.pacnew}

deepsea22 commented on 2025-12-03 14:21 (UTC)

After updating to latest, photoprism throws this error on startup: ERRO[2025-12-03T15:20:05+01:00] config: invalid models path, check configuration and permissions What am I doing wrong? I have not customized anything but the storage path, which worked fine previously.

krutoileshii commented on 2025-09-07 22:36 (UTC)

@AlynxZhou you know you can just overwrite the settings in the defaults.yml inside of the options.yml Since this package doesn't provide options.yml it should keep your settings between updates.

shtrophic commented on 2025-08-08 20:38 (UTC)

Thanks for noticing @Alynx/hou

AlynxZhou commented on 2025-08-08 13:22 (UTC)

@deepsea22 First install MariaDB and setup it (just follow Arch Wiki), and then create an user for PhotoPrism (I'll just use photoprism), set a password for it, then create a database for PhotoPrism (I'll call it photoprism too), and grant all permission for this user in this database.

And then you need to set following in options.yml to make PhotoPrism use MariaDB:

DatabaseDriver: mysql
DatabaseName: photoprism
DatabasePassword: your_database_user_password
DatabaseServer: /run/mysqld/mysqld.sock
DatabaseUser: photoprism

If your are using different machine for PhotoPrism and MariaDB, use IP:port for DatabaseServer instead of UNIX socket.

AlynxZhou commented on 2025-08-08 05:22 (UTC)

Hi, could you please add backup=("etc/${pkgname}/defaults.yml") to PKGBUILD? I've modified defaults.yml to use my own directories, and I find when I rebuild and reinstall the package, it just replaces my modified defaults.yml.

deepsea22 commented on 2025-06-10 06:57 (UTC)

Is there some guidance on how to use the mariaDB backend with this package? Documentation (e.g. https://docs.photoprism.app/getting-started/advanced/migrations/sqlite-to-mariadb/) seems very sparse.

shtrophic commented on 2025-04-25 14:03 (UTC) (edited on 2025-04-25 14:04 (UTC) by shtrophic)

Please note: since upstream switched to tensorflow-2.x, there is no need anymore to vendor a compatible tensorflow version as the photoprism-tensorflow-* packages.

I also chose to vendor the model weights again, to simplify everything. (effectively un-doing the efforts of the previous maintainer, who chose to create a new package for every zip/tarball. It is definitely an opinionated change, but it should have no effect on end-users).

Therefore, this package now depends on tensorflow (which can be either -opt,-cuda and so on) and conflicts/replaces phoroprism-{nasnet,nsfw,facenet}.

1 2 Next › Last »