I don't remember specifics, though I can find out; I have it seemed in Kubernetes with hand written manifests. I had to tie Photoprism to a specific node which had had more resources than it's peers; I would have to refer to the manifests to recall which DB I used. All storage was over NFS (meaning the storage speed was limited by my 1Gb network backbone), which probably created some of the resource issues.

Edit: as for my tool, it won't replace Photoprism, its primary goal is to deduplicate your photo library.