• 0 Posts
  • 7 Comments
Joined 3 months ago
cake
Cake day: September 10th, 2025

help-circle
  • So many upvotes without a comment :/ Sadly I don’t have much useful info to add either, I’m looking forward to how others do it as well, since I recently noticed this panel in Beszel too.

    Honestly, I use the status icons in Homepage dashboard as a health check, since I always use my dashboard to navigate to apps. Red status indicator -> I have to go fix it. Nothing more severe.

    But for point 3 I do have a strong hunch that it depends on the container image creator - a health check is usually just a command that either succeeds or not (or a http response that gets a 200 or not), so it can be as simple as pointing a request to the root url of the app. Of course, this is not the most performant way to check this, which is why app makers may also put in explicit liveness/readiness or similar endpoints that return a really short json to indicate their status. But for the containers that have a healthcheck, they must be implemented in the image (too) I think






  • I’d take a shot at super speed, I feel like simply saying “but your physique stays as-is” would be enough of a limitation with the following notes:

    • You can decide to speed up your perception and run up to e.g 20x your base speed. That would make a 6 km/h walking speed into 120 km/h. Maybe we can do 50x and then it’s 300 km/h.
    • Your body experiences the physical task as if you did it at base speed. You exercise for 10 minutes, the physical toll is 10 minutes, even if you sped yourself up to 50x in that timeframe.

    In one second, you could zip through 80 meters just by walking, quick enough to be super useful, but still possible to counter since you will get tired after a while