I’m new to self-hosting, and I’ve stumbled upon Homer which seems like a good tool. However, it’s real tedius to go through editing the config file VIM based constantly.
So I’m just wondering if there exists any GUI based editors or generators out there, that allows me to specify the number of service groups and what service items that are in the group, and then get that exported as a .yml file.
If there is no tool out there, I’m considering just creating my own. But before sinking in those hours, I thought I might as well quickly ask in here and see if such a tool already exists?
I use Hajimari which takes all my ingresses and turns it into a dashboard automatically.
Requires running kubernetes though
If you run docker i like homepage, since it has auto discovery based on service/container labels. So if I deploy a new service i just add some labels to the compose file and boom it’s on homepage.
I am not aware of any “generators” like that, but some personal dashboards can be configured through the UI instead of config files.
Check the projects listed here: https://github.com/awesome-selfhosted/awesome-selfhosted#personal-dashboards
I’m new to self-hosting […] it’s real tedius to go through editing the config file VIM based constantly.
You better get used to it since selfhosting many projects involves that. And maybe try to use
nanoinstead ofvimas editor.Using a “OS” like /r/CosmosServer or CasaOS for managing your services can also be useful for a beginner.
You better get used to it since selfhosting many projects involves that.
That’s fair, and I can easily use it. I do it a lot when working with Docker, and handling servers at work. I just prefer a ‘proper’ GUI when it’s something like working with a large yml file.
Also, maybe ‘generator’ was a bad word to use. I meant an editor. That was my bad. Another commenter suggested “Homarr” which I’ve set up now. There are some annoyances, such as: a category having to fill 100% of the width; or categories being just large in general. But I’ll play around with it some more, see if I can’t get it to be as I want.
I think Dashy is the one that gained a lot of popularity, is quite powerful and has option to add things via GUI, it’s great.
There is “homarr” which is much easier than homer. It doesn’t auto generate but creating the dashboard is gui based
Nice! Really appreciate that, that was precisely what I was looking for.
So thanks for that!
No problem! I just started using it a few days ago and like it a lot so far.
Yes, there is a fork of homer named bender which was a fork of homer that was made some time ago but I think it got discontinued (I still use it though). It works awesome.
All the configuration is done via GUI:
I like Homer but I also like Flame, which is configured by GUI
Same here. I didn’t need all of the fancy data about my systems. I’ve got uptimekuma for that.
I needed a quick one pager of all of my shortcuts to my self hosted services. Flame does it well and is very light weight.
Lots of other people have suggested alternative dashboard software, but have you considered using Visual Studio Code? It’s not a GUI editor, but it’s leagues better than VIM or nano.
Instead of using VIM or some other Linux editor to edit files in the command line, I recommend setting up VS Code or Code Server so you can make changes there. This is what I currently do. I then push the changes to my Gitea instance and then use wget to move them to my homer directory. Allows me to keep track of changes I made that may potentially break homer AND if something happens to corrupt the file, I always have a backed up source. I need to get into the habit of doing this for the countless number of container compose files I’ve got all over the place.
Absolutely, using a more powerful text editing tool, or just one more user friendly, that’s a good idea! But it’s not really VIM that’s the annoying part for me, rather just having to write so much of the “same” text. Which was why I was curious about any GUI based editors for it.
But it’s still a really good idea, especially using version control for the config files.