🔍 Unsure which Open edX release you are running? Check it instantly here!

Community Show & Tell
1

Hi everyone! :waving_hand:

Have you ever looked at your Open edX platform and wondered:

“Is this site running on Quince? Palm? Or are we still back on Nutmeg?”

Sometimes, unless you have direct access to the server console, it isn’t immediately obvious which release version your community site is using.

We built a small, free tool to help solve that mystery quickly.

:rocket: Check your Open edX version here: https://openedxcheck.aulasneo.com

Open edX Version Checker - by aulasneo

Why does the version matter?

Beyond just knowing the name of the release, staying aware of your version is crucial because:

  • :shield: Security: Older, unsupported versions may miss critical security patches.

  • :sparkles: Features: You might be missing out on the newest features and UX improvements.

  • :wrench: Maintenance: Ensuring your dependencies and software stack remain supportable.

Feel free to give it a try and let us know if it helps you identify your platform’s status!

Thanks!

6 Likes
2

Hi @estebanetcheverry
Not sure if this is an issue on my side, or maybe it’s picking up incorrectly, as I’m running the default teak.2 release at https://github.com/openedx/edx-platform.git#release/teak.2 but your site tells me I’m on master branch. Maybe a bug or maybe I’ve missed something on my side :slight_smile:

1 Like
3

Hi @joel.edwards!

You’ve found something interesting. The release line in Teak is reported as ‘master’. This may be an oversight during the release phase. I’ll report it.

2 Likes
4

Thanks for sharing this!

It’s a super useful tool for quickly checking the Open edX release version.

Much appreciated!

1 Like
5

Thanks for sharing this, Esteban! Very handy. I work in Business Development and this is quite useful as many clients aren’t aware of their current version. I’m wondering if it’s possible to determine the version for instances with custom dashboards? Right now it looks like custom dashboards return a not detected result.

1 Like
6

Thank you, Esteban. This tool is very cool. I always wanted to have such to define which version the client has. I just noticed that if the project has also a Portal, it can’t detect the release version. I think a commenter above meant the same case.

7

@jordan, try adding /api after the LMS URL. Even if an instance uses custom error pages, this approach should bypass them and render the native 404 page from the LMS. Currently, the meta[name="openedx-release-line"] HTML node is added only on pages rendered with Django templates (the legacy experience).

cc: @Yana_Lovyagina

2 Likes