# Identify state of stack in admin UI to prompt upgrade when required

**URL:** <https://meta.discourse.org/t/identify-state-of-stack-in-admin-ui-to-prompt-upgrade-when-required/329316>\
**Category:** Feature\
**Created:** [October 4, 2024, 8:03am UTC](https://meta.discourse.org/t/identify-state-of-stack-in-admin-ui-to-prompt-upgrade-when-required/329316 "2024-10-04T08:03:53Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Amicable](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/amicable/32/68902_2.png) [@Amicable](https://meta.discourse.org/u/Amicable)\
**Post date:** [October 5, 2024, 4:32pm UTC](https://meta.discourse.org/t/identify-state-of-stack-in-admin-ui-to-prompt-upgrade-when-required/329316/3 "2024-10-05T16:32:01Z")

</div>

Thanks for that! I’m a bit surprised it’s so tricky. I was thinking I could expose an endpoint (/admin/os\_info) that gathers OS info using basic sys commands & then use Ember to create an admin route & get that info into a simple template. Even better, maybe that someone had already done sthg similar that I could adapt for a simple solution.

But thanks anyway for your pointer. I was hoping to help others that might stall like I did with a largely hands-off installation only to find it seizes up after a few years. I guess I’ll just login more often 😄

---

_[View the full topic](https://meta.discourse.org/t/identify-state-of-stack-in-admin-ui-to-prompt-upgrade-when-required/329316)._
