Difference between `overhangio/openedx:20.0.2` and `overhangio/openedx:20.0.2-indigo`

Does anyone know what the differences are, if any, between these two images? I tried to see what the differences with the Dockerfiles are with indigo enabled or disabled by the tutor plugin but I couldn’t see any differences for the main docker image (openedx-mfe there are a few clear differences). I see that

javascript_files = ['base_application', 'application', 'certificates_wv']
dark_theme_filepath = ['indigo/js/dark-theme.js']

for filename in javascript_files:
    if filename in PIPELINE['JAVASCRIPT']:
        PIPELINE['JAVASCRIPT'][filename]['source_filenames'] += dark_theme_filepath

MFE_CONFIG['INDIGO_ENABLE_DARK_TOGGLE'] = True
MFE_CONFIG['INDIGO_FOOTER_NAV_LINKS'] = [{'title': 'About Us', 'url': '/about'}, {'title': 'Blog', 'url': '/blog'}, {'title': 'Donate', 'url': '/donate'}, {'title': 'Terms of Service', 'url': '/tos'}, {'title': 'Privacy Policy', 'url': '/privacy'}, {'title': 'Help', 'url': '/help'}, {'title': 'Contact Us', 'url': '/contact'}]

Also gets added/removed to the settings but presumably this only gets interpreted if indigo is installed, so could actually still be there if it’s not installed and it wouldn’t change anything, right?

If it’s basically the same, does that mean that for that image (and the lms/cms) basically the only difference is that there is an assign_theme() that gets applied in a job? If I just delete the values from theming_sitetheme it looks like it goes back to the default for the lms/cms(/preview)…

Yes, Indigo is a theme plugin, and the -indigo image is built with Indigo assets included so that Tutor’s Indigo plugin can safely reference its styles, templates and overrides.
For LMS/CMS, there are usually no obvious code-level differences to find when comparing images. Indigo works by overriding settings, theming and branding at runtime, rather than by modifying edx-platform itself.

If I delete the values from theming_sitetheme it looks like it goes back to the default for the LMS/CMS

Yes — that’s exactly how it works. Indigo applies its changes to LMS/CMS at runtime, and removing the assigned theme reverts the site back to the default Open edX theme.
But this is not the case for MFEs, though as Indigo also introduces build-time changes for MFEs i.e. branding, header/footer configuration and dark-mode support are compiled into the MFE bundles. Because of that, MFEs must be rebuilt to add or remove Indigo behavior correctly cause there might be some configs that gets missing if we disable indigo plugin and don’t rebuild MFE image.

I hope this answers your question, but we can discuss this further if needed.