glitchtip-backend VS OmniDB

I draw ones attention to the actual Open Source glitchtip which has a much more sane deployment, akin to the good old days of Sentry before they got Big Data-itis: https://gitlab.com/glitchtip/glitchtip-backend/-/blob/v4.0.8... (or its helm version, similarly not JFC https://gitlab.com/glitchtip/glitchtip-helm-chart/-/tree/61c... )

For self hosted Sentry, look at Glitchtip (https://gitlab.com/glitchtip/glitchtip-backend/-/blob/master...)

GlitchTip describes themselves as a "partial fork/mostly re-implementation"- https://gitlab.com/glitchtip/glitchtip-backend

Early versions of it I beleive used more Sentry code. SlIf Inrecall correcrly their initial release was basically a renaming of the open source sentry code. It has taken its own direction since.

Can you support GitLab? GlitchTip meets that criteria.

I'd be happy to walk you through contributing to GlitchTip. It uses DRF. https://gitlab.com/glitchtip/glitchtip-backend

GlitchTip (my project) uses DRF including model viewsets, serializers, nested routers, and class based permissions.

OmniDB is a collaborative open-source database manager that’s available as a hosted version or as a stand-alone app. The application is built keeping simplicity in mind, making it one of the most user-friendly database managers.

This is a fork of a fork of https://github.com/OmniDB/OmniDB? Because they both havent any recent activity?

Missing this: https://github.com/OmniDB/OmniDB

The only thing that concerns me is the state of the project https://github.com/OmniDB/OmniDB/issues/1289

I use OmniDB, an open-source application for managing databases. Version (3.0.2b) of OmniDB does not have an option for selecting and dropping multiple databases. To drop a database in OmniDB, you right-click on a database, select Drop Database from the context menu, run the query to drop the database, and finally close the query window. The thought of repeating the four steps on all those test databases led me to think of other efficient alternatives.