Can't access phototview web ui with k8s configuration. about photoview HOT 4 CLOSED

Thanks for the confirmation. I already launched photoview with k8s and it works well. Thank you again for your hard work.

from photoview.

Hi @googollee, thanks for your report.
We do not officially support k8s, as (as far as I know) nobody has tested the deployment of Photoview onto k8s.
However, I noticed a few things in your config:

• you use SQLite DB and it is a strange choice (as to me) for k8s deployment. Currently, we have limited support of SQLite for really small deployments with rare access from users (as it is connected to the backend in exclusive mode using a single connection). I'd recommend you switch to PostgreSQL, as this is the most performant DB and fits the best to a k8s setup, where a higher-than-usual load is expected.
• you've mixed paths inside the container: you used the release image while setting paths from the master branch. I'd suggest you switch to the viktorstrate/photoview:master to be consistent and get the latest fixes and improvements.
• make sure that the value of the PHOTOVIEW_UI_PATH points to the folder inside the container, where the UI files are located. For the master image that should be the /app/ui

Please try these (at least the last 2) suggestions - hope that they will help. If not, please share what has changed in the app behavior after these changes were made.

from photoview.

Hi @kkovaletp,

Thank you for the quick response.

It's working with viktorstrate/photoview:master and PHOTOVIEW_UI_PATH=/app/ui. I didn't know that viktorstrate/photoview:2 is a 2-year-old image. I followed with docker compose example and it should be updated. I'll see if I can do that later.

Now from the log, it keeps complaining that the database is read-only. I hope to keep it simple as a single instance.

from photoview.

I followed with docker compose example and it should be updated

Actually, this is a tricky moment, as this is the default branch, the example should refer to the released image, however, until the current master image is not released, there is this inconsistency.
I don't think that updating the example to refer to the unstable version of the image is a good idea, but I confirm that there is inconsistency, which leads to user misunderstanding and product misconfiguration.

from photoview.