GlitchTip now supports Norwegian Bokmål (thanks to Gitter user blixhavn). We are now accepting contributions for more languages. See glitchtip-frontend for more information on contributing. More work is necessary to mark translatable strings.
As of version 1.12, GlitchTip already supported Releases. These are used in filtering and to facilitate sourcemaps to view the original source. With 2.0, Releases are now visible in the web interface, as well. This improves visibility and can assist users with adding sourcemap support to JavaScript projects.
GlitchTip will now use semantic versioning to indicate potentially breaking changes for self-host users. Version 2.0 changes some deployment-related environment variables. Smaller instances can safely ignore this. If you change uWSGI and celery environment variables, however, you'll need to make the following updates:
MAX_WORKERS
becomes UWSGI_WORKERS
MIN_WORKERS
becomes UWSGI_CHEAPER
INITIAL_WORKERS
becomes UWSGI_CHEAPER_INITIAL
CONCURRENCY
becomes CELERY_WORKER_CONCURRENCY
GlitchTip now uses upstream uWSGI and Celery defaults. If you'd like to use the prior GlitchTip defaults, they were:
We recommend setting CELERY_WORKER_CONCURRENCY, and will continue to set this default value in our sample docker compose file to 2. The Celery default is the number of CPUs. This could cause instability on systems with a large number of CPUs where it's not desired for Celery to consume all system resources.
The purpose of this change is to get more in line with existing upstream environment variable names. The new defaults should also be lighter on system resources. Refer to the GlitchTip installation documentation for more info.
Your time and financial donations are the only thing that keeps GlitchTip development going. GlitchTip is not backed by venture capital.