Self hosting questions. #2318
Replies: 1 comment 2 replies
-
the second - "it always be the version that exists at the time the container is created". To update to the latest, you can:
These steps will recreate your container, but since the data is kept it volumes (https://github.com/ente-io/ente/blob/main/server/compose.yaml#L86), when the new container starts with the new code from the updated image, it'll just use the existing data, so your data will be preserved across updates.
These are not basic questions though 🙂 and I can empathise with you trying to find a answers. But I can't answer them for you, since the approach depends on your risk-tolerance (of potential data loss) and convenience. If you just want to play around, then the second approach ("create a VM, install Docker, and make sure the VM just always has enough storage available for however many photos I have") is fine. For more serious use, you'll need to ensure that volumes that I mentioned - (a) the database (the postgres-data volume in the sample docker compose file), and (b) the object storage (this is where the encrypted blobs are stored, this is the minio-data volume in the sample docker compose file) are stored in a way that is not tied to the lifetime of your containers, and are also backed up somewhere. A middle ground (not suggesting you do this necessarily, I'm just mentioning this so you're aware since this might be a possibility that you could help you get started) is to not rely on self hosted ente as the primary source, but instead do backups from your clients. That is:
2 is anyways a good option anyways even if you have a more solid self hosted setup. This export will not be E2EE, but it is also not tied to Ente in any way, so even if your self hosted setup breaks, you should be able to reimport this into Ente (or wherever else you wish). |
Beta Was this translation helpful? Give feedback.
-
I have searched through the discussions for “self host” and “docker” and couldn’t find these answers, but I apologize if I missed them and asked again.
I would love to self host this, but am new to self hosting.
If I follow these instructions https://github.com/ente-io/ente/blob/main/server/docs/docker.md will the docker container update as Ente updates or will it always be the version that exists at the time the container is created? How can this be manipulated to point the storage of Ente to an SMB share that’s on a truenas or Unraid machine? Do I just need to create a VM, install Docker, and make sure the VM just always has enough storage available for however many photos I have?
I know that these questions will seem basic, but they honestly are a complete mystery to a beginner. (Also feel free to recommend resources where I can learn more about docker in general!)
Also, thank you to Ente for open sourcing such a legit project (even if I don’t fully understand how to implement it yet 😅). My intent is to learn how to self host this while paying an annual 2TB plan to support the project as it continues! Nice to have a legit alternative to Google Photos!
Beta Was this translation helpful? Give feedback.
All reactions