Questions regarding these builds about photoprism-builds HOT 12 CLOSED

Hi! I'll try and answer as best as I can, but please understand I'm no expert either. I just fumbled around long enough to get something that works well enough for my purposes.

• As per the Readme.md, only amd64 hardware can run your builds? Our Yunohost package support the installation for amd64, arm64 and armhf (armv7). Those hardware wouldn’t be able to run the actual builds?

Correct. Currently only amd64 is supported, because that's the architecture that Github Actions run on.

I see there is a way to run jobs on other architectures using QEMU, but I haven't actually tested it myself.

• Does your builds are also glibc specific or are they glibc independent? Would they work on Bullseye and Bookworm with different glibc versions? (I’m quiete a learning newbee, just saying if this make no sense 😛)

Bullseye works fine, it's what the Docker image is based on that I'm using for these builds (photoprism/develop:bullseye), and it's what I'm using for my personal server. I briefly tested the latest build on Bookworm and Jammy as well, and both seemed to work as well, at least to the point of loading the UI and being able to log in. I can't guarantee anything beyond that, though.

from photoprism-builds.

Thanks for your fast answer!
I will then try already with the present build before builds from other arch can be made. I will maybe try but the result is quiete uncertain.

from photoprism-builds.

I’ve finally found the time to try your builds, install works but I have frontend issues… (exactly the same as https://www.reddit.com/r/selfhosted/comments/v5qcpn/photoprism_on_ubuntu_troubleshooting_frontend/ where you have tried to help if I understand well).

I try anyway, if you have more ideas now what could be the issue?

I am trying to package it for Yunohost with approximatively the same procedure as your guides.

Thanks for your help!

from photoprism-builds.

Sorry, I don't think I have any more insight into the workings of the PhotoPrism front-end than in that Reddit thread you linked to.

What sort of platform is the install running on? I'm not familiar with Yunohost at all.

A few of the errors, as far as I can tell, seem to refer to some resources being blocked. Could it be due to some browser extension or privacy-related setting?

from photoprism-builds.

Thanks for your answer!
Yunohost is Debian-based. I don’t know what I can tell more?

I have tried on Firefox and Brave, both without privacy extensions enabled to be sure, same problem.
If you don’t know, I don’t want to take your time too much, I only tried if you had an answer :)

Do you use nginx? With the same config as proposed in PhotoPrism documentation? Or did you add some things?

from photoprism-builds.

Yunohost is Debian-based. I don’t know what I can tell more?

I meant, does it use any sort of virtualisation or containerisation under the hood?

Do you use nginx? With the same config as proposed in PhotoPrism documentation? Or did you add some things?

I do use Nginx as a reverse proxy for my self-hosted apps. I have a template that I start from, so there might be differences from the PhotoPrism docs; I'll try and compare later.

Do your problems only occur when accessing PhotoPrism through Nginx? Or also when accessing the PhotoPrism web UI directly (port 2432 by default)?

from photoprism-builds.

I meant, does it use any sort of virtualisation or containerisation under the hood?

No we don’t use Docker or other. The best practices in Yunohost are:

• build from source -> but building PhotoPrism require a great amount of resources for some servers
• install from release -> but PhotoPrism only supports Docker atm. So we currently use a docker-extraction script but it has some limits, like the fact that the Photoprism build is made on latest Ubuntu with a higher version of glibc which makes it incompatible with Bullseye.

Do your problems only occur when accessing PhotoPrism through Nginx? Or also when accessing the PhotoPrism web UI directly (port 2432 by default)?

Unfortunately, in Yunohost I can only access through Nginx, so I cannot compare…

The PhotoPrism maintainers thinks there’s a problem with the build of the frontend (although they doesn’t seem to have looken at the issue deeply (photoprism/photoprism#3656)

from photoprism-builds.

I see from the linked issue that you can get a working PhotoPrism setup using Docker Extract, and that the front-end assets look similar to the ones in these builds. Are there any differences? What if you replace the front-end assets from this build with the ones you get with Docker Extract?

Also, have you tried running these builds on their own, in a standard Debian VM, without Yunohost or an Nginx proxy?

from photoprism-builds.

What if you replace the front-end assets from this build with the ones you get with Docker Extract?

Excellent idea! It doesn’t work either: same result. So it doesn’t seem to be an issue with the assets of your builds, but somehow they cannot be found.

Also, have you tried running these builds on their own, in a standard Debian VM, without Yunohost or an Nginx proxy?

Not yet unfortunately.

from photoprism-builds.

For reference, here's my Nginx config (with minor redactions):

server {
	listen				443 ssl http2;
	server_name			album.example.com;

	access_log			/var/log/nginx/access.log;
	error_log			/var/log/nginx/error.log warn;

	location / {
		proxy_pass		http://127.0.0.1:2342;
		proxy_set_header	Host $host;
		proxy_set_header	X-Real-IP $remote_addr;
		proxy_set_header	X-Forwarded-For $proxy_add_x_forwarded_for;
		proxy_set_header	X-Forwarded-Proto $scheme;
		proxy_http_version	1.1;
		proxy_set_header	Upgrade $http_upgrade;
		proxy_set_header	Connection "Upgrade";
	}

	# SSL
	ssl_certificate			/etc/letsencrypt/live/example.com/fullchain.pem;
	ssl_certificate_key		/etc/letsencrypt/live/example.com/privkey.pem;
	ssl_trusted_certificate		/etc/letsencrypt/live/example.com/chain.pem;

	# additional config
	include				snippets/security.conf;
	include				snippets/general.conf;
}

# HTTP redirect
server {
	listen				80;
	server_name			album.example.com;

	location / {
		return 301 https://$host$request_uri;
	}
}

As I mentioned, this is based on a template I use for a number of self-hosted apps, with only minor differences (the server_name and proxy_pass directives, mostly).

You should also look at Nginx logs and see if there are requests for front-end assets, and whether those requests are successful.

from photoprism-builds.

Thank you!
My nginx looks close to yours though.

I don't have any clue of the reason of this issue so I will stop looking further for now. I will try sometimes with new PhotoPrism updates, who knows?

Thanks again for your help here and for all your work providing installation methods to install PhotoPrisp without docker! 🎉

from photoprism-builds.

Fair enough, sorry I couldn't be of more help. Good luck!

from photoprism-builds.