blog/2025/02/24/ente-self-host-the-google-photos-alternative-and-own-your-privacy/

[giscus[bot]]

blog/2025/02/24/ente-self-host-the-google-photos-alternative-and-own-your-privacy/

Tutorial on self-hosting Ente (Google Photos alternative) using Kubernetes, with deployment and CI/CD setup via GitHub Actions for enhanced privacy.

https://developer-friendly.blog/blog/2025/02/24/ente-self-host-the-google-photos-alternative-and-own-your-privacy/

[Sandeepbreddy]

Hi Azad,

Trying to work on ente to deploy using k8. I created all the files, created Postgres in separate namespace and exposing that with external IP. Now am seeing below error while trying to execute museum deployment

panic: dial tcp [::1]:5432: connect: connection refused

goroutine 1 [running]:
main.setupDatabase()
/etc/ente/cmd/museum/main.go:849 +0x338
main.main()
/etc/ente/cmd/museum/main.go:124 +0x44c

Am not sure if its because of permission of museum file am not sure.

Can we connect in your free time to resolve this issue

[meysam81]

Dear @Sandeepbreddy

You are having connectivity issue from your ente-server to the PostgreSQL host.

If you are deploying them in different namespaces, the format will be <service-name>.<namespace-name>.

Additionally, make sure the credentials are correct.
To verify things before deployment, you can run psql commands from the same namespace as the ente-server like the following:

DATABASE_NAMESPACE="db-ns"
DATABASE_SERVICE_NAME="postgres"
ENTE_NAMESPACE="ente-ns"

DB_USER="ente"
DATABASE_NAME="ente"

kubectl create job psql -n $ENTE_NAMESPACE \
  --image=postgres:17 -- sleep 3600

kubectl exec -it -n $ENTE_NAMESPACE job/psql \
  -- psql -U $DB_USER -W -d DATABASE_NAME \
  -h "${DATABASE_SERVICE_NAME}.${DATABASE_NAMESPACE}" -c 'select 1'

One last recommendation. If you don't know your way around Kubernetes, docker-compose deployment is a better fit for you.

Regards.

[Sandeepbreddy]

Am actually learning K8 and trying to move apps to k8. What you mentioned is true so I moved variables from configmap to env variables within the deployment and able to resolve above error.

Thank you,
Azad