Upgrade discourse fails from 3.3.0 beta1 to beta2 via admin panel

[RBoy]

The solution appears to be to manually rebuild the image from the cli via ./launcher rebuild app.

Upgrade / Rebuilds Fail due to MaxMind DB EOL

We now support the officially supported way of obtaining databases per: https://github.com/discourse/discourse/commit/a8ffb6949c76ea16e96ec4d45e6524cd8cc42c2d If you wish to get regular MaxMind updates you will have to head to GeoLite2 Sign Up | MaxMind to register an account and generate a license key. Then you would amend your container to include it in the env: section: env: DISCOURSE_MAXMIND_LICENSE_KEY: ...key here... The fix ensures there is no time bomb anymore. If we have no lic…

Don’t know why it would throw a MaxMind error while upgrading docker_manager via the web admin console (from 3.3.0 beta1 to 3.3.0 beta2-dev) but works via the CLI. Maybe there needs to be check via the web console upgrade docker_manager to not upgrade MaxMind until the dependencies are updated?