Landing page for all my services
-
I've been using a modified and simplified version of Prismatic Night it's somewhat basic but I'm pretty happy with it. I've got startpages for my personal stuff, one for my wife and her personal stuff, and a couple for work.
-
Ah personalized ones, also a good idea
-
That's what I use. It goes under the radar a lot and I don't know why. I love that it shows me my sabnzb downloads and what streams are happening on Jellyfin at a glance.
-
I think this is possible nowdays.
-
Static, hand coded html. You can be as pretty as you want to be. A good learning exercise and since it is all static it will be fast and won't have more security issues.
-
Yeah; the lack of authentication options is a bit of a bummer if you're going to expose/share this page. There is always basic_auth in nginx or whatever proxy you're using if you really want.
-
In that case. Homarr is awesome, no complaints.
I probably won't retroact this, my family aren't going to explore and it was more to keep them on their specific homepage and stop them getting lost. New users will be locked to their specific page, I don't expect they'll ever go exploring to find out.
-
Or if you want to learn a JS framework, you can also do it that way.
-
There are a bunch of other static site generators as well. They're mostly targeted at blogs and whatnot, but maybe that's a good thing if you want to leave some instructions/documentation about each one.
-
If you want some ideas, there are plenty of examples here:
https://old.reddit.com/r/selfhosted/search?sort=new&restrict_sr=on&q=flair%3APersonal%2BDashboard
-
I use wiki.js in the linuxserver.io flavor. I have 3 URLs for every service I run: public, LAN, and tailscale url. My "homepage" is a big markdown table with links to all the services. It's not pretty by any means, but it's very functional
-
Homepage.dev
-
I like homarr.
-
I just made a landing page in HASS, if you're already running three instances could you make a page in one?
-
Similar, but more fancy, I have a bash script that runs every 15 minutes and ingests a config file. The config file has a super simple CSV format of every service I have. It checks that all the services are operational and generates an HTML file from it. If any services are down the HTML will show its down, otherwise its just a helpful link.
-
Hm, so you just used some cards to make links and icons somehow for that? But then I would need to replicate it on at least my dads and our instance.
-
Yep, here is the yaml but redacted
- type: entities title: Communication entities: - type: weblink name: Webmail url: https://postale.io/ icon: mdi:email - type: weblink name: Mattermost url: https://mm.stuff.com icon: mdi:chat - type: weblink name: Mumble Server url: https://mumble.stuff.com icon: mdi:radio-handheld -
I run my website as static site from within a Docker container, I wonder how I would get the information about the other containers into that site.
Do you directly serve that site from the host or do you run the script and write something in a volume the site has read access to or bind a file?
-
I host it on the host that runs the script and proxy it. I have one mission critial pi that is my uptime bot, pi hole and backup VPN if my elaborate server falls on its face. But you could easily use docker volumes too, and have the script push to that folder.
-
I think you pretty much just now wrote a landing page, you just need to turn those into links and host that page somewhere.
