[Announcement] Finally! We revamped our self-hosting documentation
Hello @everyone!
After gathering feedback from several self-hosters in the community, we have revamped our self-hosting documentation.
What's new?
- Restructuring self-hosting documentation for better navigation and user flow
- Coverage for 3 installation methods (Quickstart, Docker Compose (from source) and manual setup) with tested configuration
- Detailed description on how to connect to various client applications to remove confusion
- Refactored documentation for administration - user management, object storage configuration, using Ente CLI, configuration of reverse proxy with Caddy.
- Configuration and environment variables for ease of use.
- Upgrading procedure for 3 installation methods for seamless usage.
What's next?
- Revamp documentation for backup
- Cover security and best practices
- Standalone documentation for Ente CLI
- Cover architectural details
- Improvize troubleshooting guides
Figured out a way to run Ente with a different method (Portainer, Unraid, etc.)? Using it on different device specifications? Feel free to contribute to our community guides starting next week.
Happy weekend, hope you have a blast if you were looking forward to self-host Ente :lilducky:
And feel free to share your review on the current documentation, it helps us improve and move forward!
19 Replies
You might have a look at an issue I had on Ubuntu 24.04 LTS
-> https://discord.com/channels/948937918347608085/1402737215649349732
-> Solved in the last post.
Have a nice day! :duckyheart:
Hi, why do you offer self-hosting? You cannot make money out of it, can you?
Quote:
>Our real aim behind open sourcing our servers is to offer yet another reason for Ente customers to feel proud that by choosing Ente, they’ve made the right choice.
Sure they need to make up for a living, but it's this attitude which instantly catches the attention. You can still have a subscription to support the team and selfhost if you want to.
In the self hosted application, i would love if there could be less config files spread around. After upgrading my setup broke and trying to debug what config is wrong im getting gray hair
I am hoping to give back via some code contributions. Opensource isn't a take only scenario.
I also had this issue, and I couldn't upload. I couldn't upload until I also changed the museum.yml to replace localhost. Then I had to docker compose down for the changes to go through, since docker compose up didn't work. Further, I cannot get this to work with a domain name and TLS, always getting CORS errors. Hopefully, the documentation will address some of this.
Do you have your S3 also configured as TLS and changed the museum config to https? I had to
I did, I was just trying to get minio working to test it out. I think I've given up and will just move to an actual bucket when I have the time to mess with it. Edit: Got it working on backblaze, but man that was some undocumented trouble on both ends.
I believe at end just a few go self-hosting.. too much trouble. So it is a good marketing
Yep, totally agree. It is the pure fact that you COULD selfhost which catches many people.
Yep, can confirm that self-hosting is a major PIA, especially on windows. But I got everything working and learned a ton. Fiddling with the architecture and playing around with different import formats gave me more confidence in migrating to the hosted offering down the road.
it still sucks use more generic commands not just commands that are debian specific
@Keerthana
use something like homebrew or make one for redhat/rocky/alma users
Hey there, we use Debian specific commands since that's the distribution used my majority of the self hosters over say RedHat, Rocky, etc
The debian specific commands can be altered for other package managers that comes with the distribution and if we are talking about init system, we assume that the person knows what they are doing instead of documenting every nook and cranny.
-# If your issue is resolved, you can use the /solved command to close the thread. If not, use /unsolve to cancel.
Windows isn't a great choice for self hosting since Docker experience isn't great on it due to virtualization inconsistencies.
@Keerthana there is no explanation on where i am getting <key> and <passowrd> from
The key and password is from your object storage's access key and password and would have been detailed in object storage config in Configuration file section.
Will check on this
postgres-1 | 2025-10-16 12:52:14.465 UTC [42] WARNING: database "ente_db" has a collation version mismatch
@Keerthana what version of ubuntu