I am the developer of Summit for Lemmy.

  • 2 posts
  • 89 comments
Joined 3 years ago
Cake day: June 13th, 2023
  • Thank you everyone for the answers. After more reflection, unfortunately I’m going with Home Assistant simply because I already have the page open on every device. It’s not pretty but it’s already basically my “home page” so might as well as add to it instead of introducing a completely different service/page.

I’ve accumulated enough self hosted stuff that I feel like I want a dashboard now so I don’t have to remember which IP & port I need for which service (not all my services are exposed to the WWW).

I looked at some dashboard solutions already but there is a huge amount of them. I also use Home Assistant as the dashboard for my home.

So I’m looking to bounce some ideas off this community. Should I add one more service to my servers in the form of a dashboard, or should I maybe create a dashboard in Home Assistant?

If going with a standalone dashboard service, which one?
If going with Home Assistant, is there some good add-ons or something I can use to make managing my services easier?

Let me know what you guys think and thank you!

Update

Forgejo seemed to be the winning answer so I tried setting it up. Total setup time was less than 10 minutes. I pushed 10 repositories to test it out and so far it seems pretty good. Thank you everyone for the answers!


As the title states, I am looking to host maybe ~100 git repositories locally on my home network.

I’m not planning on doing anything too crazy with my repositories. The solution doesn’t need to support like 1000s of contributors however it should support the most basic features such as being able to see individual commits, branches, diffs, maybe some PR related mechanism, a web GUI, etc.

I don’t like to tinker too much. The solution should work and be stable. Stability is a hard requirement. I want to write code and not have to worry about losing it. Yes I will make backups.

Please let me know what some of the best options are at the moment. Thank you!

  • I mostly don’t use AI… At least not directly for programming. I use it for other things like translating, formatting text, etc. i sometimes ask AI to make something for prototyping purposes.

    I will occasionally ask AI to solve programming problems, more to keep up with current trends. I like to keep informed with what AI can and cannot do because even if I choose not to use them, the same will not be true with my coworkers or other people I interact with. Having a good understanding of the current “meta” for AI lets me know what to look out for in the context of avoiding disasters.

  • I’ve had this problem with abstractions for the longest time. Of course whenever I say anything negative about abstractions I just get dog piled so I don’t usually like to discuss the topic.

    I think abstractions as a tool is fine. My problem with abstractions is that most developers I meet seem to only talk about the upsides of abstractions and they never take into account the downsides seriously.

    More often then not, I just think people treat abstractions as this magical tool you cant over use. In reality, over use of abstractions can increase complexity and reduce readability. They can greatly reduce the amount of assumptions you can make about code which has many many additional downsides.

    Of course I’m not saying we shouldnt use abstractions. Not having any abstractions can be just as bad as having too many. You end up with similar issues such as increased complexity and reduced readability.

    The hard part is finding the balance, the sweet spot where complexity is minimized and readability is maximized while using the fewest amount of abstractions possible.

    I think too often, developers would err on the side of caution and add more abstractions then necessary and call it good enough. Developers really need to question if every abstraction is absolutely necessary. Is it really worth it to add an additional layer of abstraction just because a problem might arise in the future vs reducing the number of abstractions and waiting for it to become a problem before adding more abstractions. I don’t think we do the latter enough. Often times you can get away with slightly less abstractions than you think you need because you will never touch the code again.

  • I was able to buy my M1 MBP from my company for cheap and the laptop is amazing. Its like 4 years old now but it doesnt feel like its aged a day. Easy 6 hour battery life while doing heavy tasks and it performs like a beast. It’s faster than my desktop at many tasks such as compilation.