-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Self-hosting feasibility #25
Comments
Currently the only way to self-host is by building a custom version of the app, and hardcoding the server uri in config.uri. At one point I wanted to make it configurable, but that requires a non-trivial amount of work since the app would need to start with a setup screen on first launch. It's not super complex though, it just takes some time. The client should work fine on Flutter web. I tested it a while ago and the only issue is that the UI doesn't really scale well to desktop sizes. I made a few token efforts to implement a master/detail UX but ran out of time for that. On the server side, a docker container would be ideal, I would be happy to accept contributions: cachapa/tudo_server#1 |
Closing in favour of #26 |
That sounds great, thank you! I'll try to contribute a docker setup sometime soon :) |
This app looks great, it's exactly what I've been looking for for a while! How feasible is it at the moment to run a tudo server on my own systems? The two limitations I see right now are:
Is there an interest in making tudo easier to self-host? Are there any other current limitations I've missed? If it is wanted, I could probably contribute the necessary parts for building and releasing docker images for tudo_server (and perhaps for the web build of the client?)
Thank you!
The text was updated successfully, but these errors were encountered: