I love Homepage. It's pretty, configurable, simple, and versatile.
Thanks! I have chosen that one for my test. But it looks like there is no access/user management available.
That's true. You must manually edit the up-to-6 config files to customize Homepage. It's not difficult, but it's not a GUI.
d.rymcg.tech is a docker-based self-hosting "platform", and it includes Homepage and a way to configure it using your own custom homepage-config repo, but that might be a bit much to take on if you just want Homepage or if thisnkind of thing is outside of your skillset.
Homepage 🥰🥰
Love it
🥰🥰 more love to homepage
This is what I was planning to use on my next build with https://www.authelia.com for the authorization gateway.
What reverse proxy will you use? And are using tunnels to get access from outside or something else?
https://github.com/geekau/media-stack/blob/main/full-vpn_single-yaml/docker-compose-media-stack.yaml
Planning to base my next build on this stack. Still waiting on a couple parts.
Have not dug through the whole thing yet, but looks like they use Swag. Haven't looked into it yet, I normally just go nginx.
I already have wireguard with dynamic dns on my router if I want to access it remotely.
I'm currently using gethomepage.dev but have also had really good luck with dashy.to
I just tested homepage but dashy looks promising. It looks like homepage lacks support for user authentication, but dashy supports it.
+1 for Dashy
Homer is the simplest
I really like Flame. I have it as my startpage on both desktop and mobile browsers. It's light and pretty quick to set up
Flame is not actively maintained anymore. Have a look at this fork which offers support for categories: https://github.com/fdarveau/flame :::
I also use Flame! I really like the clean and simple look and it’s really easy to set up.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| Git | Popular version control system, primarily for code |
| HTTP | Hypertext Transfer Protocol, the Web |
| nginx | Popular HTTP server |
2 acronyms in this thread; the most compressed thread commented on today has 9 acronyms.
[Thread #197 for this sub, first seen 8th Oct 2023, 04:25] [FAQ] [Full list] [Contact] [Source code]
(Writing plain html looks to ugly for me 😉)
no joke an ISP I use to work at had a internal static HTML page where we linked all the internal tools.
Similar, at a company they asked the person cataloging the systems to write a yaml, then a dev wrote a script that converted it to html and then they asked a designer to slap some CSS on it. I don't think it took more than an hour of each person's time. Plus you can do each stage individually and improve it over time. For example later yet someone put the yaml in a git repo and threw together a simple deploy, someone made a script that pinged systems periodically etc.
At that point you're just reinventing a monitoring system.
For proper monitoring yeah, I'm just saying it's faster to write a HTML page than to install a homepage app that won't detect half your stuff properly anyway.
I'm currently using Homarr but have used Fenrus and a few others and all work well you just need to find the one you like the best. The two I mentioned are simple to use and very customizable.
I use Authentik, primarily as a local identity provider, but it shows links to all my services (and auto logs-in to supported ones)
This is what I use. You write code in markdown, ipynb Python, or HTML and CSS and it builds the static website HTML automatically.
There are free styling Python packages to generate CSS too!
I host on GitHub pages for free.
I personally use https://dashy.to/ because you can also add links to your externally hosted services should you want to.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!