External integration on GitLab and Codeberg

Delivered features
2

Hi @ArMour85,

Thanks for the request. I’ll explain frankly why this won’t happen, rather than leaving the topic hanging.

The external integrations system doesn’t just point to a repository; it relies on the GitHub ecosystem in two places:

  • Discovery: I scan GitHub via a topic to automatically find published integrations, which avoids any manual validation process on my part
  • Publishing: The template provides pre-written GitHub Actions that build and publish the Docker image, so you don’t need to configure any CI

Supporting GitLab and Codeberg would mean rewriting and maintaining these two components three times, with three APIs, three CI systems, and three sources of bugs to debug. And the problem isn’t just threefold: GitLab and Codeberg are just two instances among thousands of self-hosted GitLab and Forgejo instances. Once you move away from the « single index » model, there’s no clear limit to where to stop.

Each added component adds monthly maintenance for years. I’d rather invest that time in device compatibility, which is the main reason people abandon Gladys today. :slight_smile:

I don’t think using GitHub is a big hurdle; all open-source projects in the market are on GitHub, and it’s an excellent solution.