What services to only host Auth?
Hey!
I have used Ente Auth offline on my phone for a while and i love the interface / how its working! But now the time has come to set up my own sync server, and i personally feel that the documentation about this is lacking quite a few things.
First of all, how do i run JUST a Auth server (if thats even possible)? I used the quick start script to setup my server but that did automatically install everything needed for Photos, Albums etc. (which i don't currently need since i'm using another solution for that) and its consuming so much unnecessary resources of my homelab. I have tried to find documentation about which services / containers are needed for which applications (in my case Auth), but i cant find anything.
So, what services do i actually need to do this? Would it be possible to separate the installation of Auth and Photos in the documentation (or just create an individual installation for them both)? And create sample compose files for JUST running the Auth server?
9 Replies
I'm sorry, I couldn't find the answer in the documentation.
-# If your issue is resolved, feel free to use the /solved command to close this thread. If you'd like to ask me another question use /docsearch
I don't think that's possible since it's using the same server
Here are my current "compose.yaml" and "museum.yaml". Im not shure if everything about the URL's are correct since i have tinkered a littlebit with them haha (and i didnt find any documentation about how endpoints etc. works š)
Oh okay yeah i understand :/ i did also notice that the Museum server seems to run both Auth, Photos etc. all together in a monolithic setup rather than as separate microservices. Everything just seems so tightly coupled rn, isnt that hard to maintain long term? š
(Not one of the developers)
But it should actually make it easier to maintain longterm, you only need to manage one thing
Im not a "pro server architecture engineer" or anything but just a mind game, wouldn't it be nice to split up Ente (mainly Museum) to microservices which run in separate docker containers? Like one Auth backend server, one Photo backend server (which is dependent on Minio), one Auth frontend etc.? And i mean for long term future proofing enabling for expansion and continued development of the project
Yeah i think it would be like that for smaller teams but wouldn't microservices (and self-contained containers) be better if / when maybe hundreds or thousands of volunteer / open source developers can work on it simultaneously? Or are you still just doing all development yourself in-house?
And for scalability and resilience in hosting, running each service as separate containers would ensure that the other services remain unaffected in case of a container crash, DDoS attack or stuff like that
-# If your issue is resolved, you can use the /solved command to close the thread. If not, use /unsolve to cancel.
Iām not exactly sure if this can be separated, but you should be able to achieve an Auth only server by removing minio and socat services from your compose file and comment out s3 section from your museum.yaml file.
In your compose file, the volumes under museum section should point to the my-ente folder where your compose.yaml and museum.yaml files are stored. The volume under postgres should point to the location of where you want the postgres data to be stored. Preferably to a data folder inside the my-ente folder.
Okay thank you so much, i will try it later!
That worked great, thanks! Maybe we (or the developers) should add this to the documentation? Or create a guide on how to install minimalistic setup for Auth?