-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
feat: Current state of this project? #1127
Comments
#655 Greetings from Switzerland too :) |
Oh I see, thanks! Yeahs seems quite a lot has already been done :) I'd love to contribute, but currently know too less to be helpful here :/. I was just trying to evaluate if there is any reasonable sense on switching to homarr now or better waiting for v1. Haha everyone from switzerland here 😅 |
Oh you can without a doubt change to homarr now, We have an importation system from the old version to make the transition as painless as possible. Most of what we do is porting old functions into a proper structure and properly rewriting it. No pressure to contribute, be free to just enjoy too. Swiss are everywhere |
Ohhh that's awesome! Thanks!! |
Describe the feature you'd like to request
Hi
I'm asking what the current state of this project (v1.0) is, are we talking about weeks till ETA or are we talking about months/years till completion?
I'm known of the other repo by ajnart of the 0.X homarr.
Sorry to ask like this here, and hope it does not sound rude, but I'm currently in a near complete rebuild of my homelab and have used dashy (
amwas a core contributor of it) as dashy has had a hard time keeping up, and the owner barely fixing critical bugs, the project has slowly become obsolete and broken, so I'm considering a full switch to homarr, however if homarr 1.0 will release in an appropriate time, I won't bother to first configure for v0.X and then for v1.x again, as I guess there will be breaking changes.Thanks for a little update :)
Greetings from Switzerland 🇨🇭
Describe the solution you'd like to see
Additional information
No response
The text was updated successfully, but these errors were encountered: