We’ve consolidated all our code into a single repository – just clone ente-io/ente on GitHub, and you will have at your disposal a state of the art, end-to-end encrypted, full stack (mobile/web/desktop clients, the server, and a CLI to boot) alternative to Google Photos and Apple Photos.
This seems a disadvantage, a single repo that does everything seems inconvenient and unnecessarily complex for a casual hobbyist that wants to try the project
The flutter apps and the electron app are unrelated to the server+web.
Same for the separate 2fa app
If you want to contribute to something you need to fork everything.
Because this contains everything that is served by ente in their commercial offer in the way that’s suited in a professional way (photos stored in S3-like storage on minio server), not just photos, also future projects you might not want to run on your server like ente lock and ente legacy
This seems a disadvantage, a single repo that does everything seems inconvenient and unnecessarily complex for a casual hobbyist that wants to try the project
How is that worse than multiple repos?
True. It’s utterly complex. Multiple repos would be much easy to fork and I’d be knowing what’s going on.
The flutter apps and the electron app are unrelated to the server+web.
Same for the separate 2fa app
If you want to contribute to something you need to fork everything.
Because this contains everything that is served by ente in their commercial offer in the way that’s suited in a professional way (photos stored in S3-like storage on minio server), not just photos, also future projects you might not want to run on your server like ente lock and ente legacy
oh ok. Haven’t thought about it like that. Makes sense
I don’t think so Tim! Just stick it all in one repo/compose file and smash the ‘go’ button. Are you paying by the directory or something?