---
title: "Comment by StackShortlist on \"I Wanted a Dashboard. I Ended Up With Five Containers.\" | Hashnode"
description: "The HOMEPAGE_ALLOWED_HOSTS bit is a good example of the config living somewhere other than where you'd look first. The point about Uptime Kuma is fair too. If a"
url: "https://hashnode.com/posts/i-wanted-a-dashboard-i-ended-up-with-five-containers/6ad16af59216b215a4cd7ab6/comment/6ad33a922fb68973c157f52f"
---

[Discussion](https://hashnode.com/posts/i-wanted-a-dashboard-i-ended-up-with-five-containers/6ad16af59216b215a4cd7ab6)

Comment [I Wanted a Dashboard. I Ended Up With Five Containers.](https://hashnode.com/posts/i-wanted-a-dashboard-i-ended-up-with-five-containers/6ad16af59216b215a4cd7ab6)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 17](https://hashnode.com/posts/i-wanted-a-dashboard-i-ended-up-with-five-containers/6ad16af59216b215a4cd7ab6/comment/6ad33a922fb68973c157f52f)

The HOMEPAGE\_ALLOWED\_HOSTS bit is a good example of the config living somewhere other than where you'd look first. The point about Uptime Kuma is fair too. If a service has a health or API endpoint, pointing the check at that instead of the login page gets a bit closer to "actually working" than "online". For Vaultwarden, testing a restore from backup before trusting it with anything real is the step that tends to get skipped.