[horde] New dev.horde.org developer site

[Simon B]

On Mon, 2 Mar 2026 at 20:47, Ralf Lang <ralf.lang at gmail.com> wrote:
>
> Hello Horde developers,
>
> I have finished some long overdue work over the weekend and it begins to
> show.
>
> https://dev.horde.org
>
> The website now updates every 5 minutes or so from the latest github.com
> updates - Pull requests, issues, pushes to git and most importantly new
> tags and releases for horde components. This is only the visible surface. I
> have expanded the horde/GithubApiClient: An OO way to access the Github API
> - partial implementation <https://github.com/horde/githubapiclient> by many
> missing commands including the necessary bits and pieces to run our
> developer tool as a "Github Application".
>
> This is only foundational. While I do use the horde/components tool as a
> testbed for new developments before unleashing them on production code,
> it's never meant to be an end of itself.
>
> The horde-components developer tool now automatically creates github
> releases when it creates new tags. See Releases · horde/GithubApiClient
> <https://github.com/horde/GithubApiClient/releases> for an example.
>
> You probably know .phar files - whole PHP applications with all their
> dependencies in one file. The horde/components tool now automatically
> releases itself as a phar file for download from the   Releases ·
> horde/components <https://github.com/horde/components/releases> page. Click
> on the arrow near "assets".
>
> This is useful for developers as it allows to just download one file and
> run a tiny script to setup a whole development install of horde with a
> simple sqlite database. This script is currently in testing and will be
> released soon. We will also add it to our CI pipelines to ensure we don't
> release obviously broken versions again. I am also preparing a version
> using the latest alpha/beta packages. For adding postgresql and mysql
> support I will probably need some assistance from fellow members of this
> list.
>
> I also fixed a nasty bug with our ticket system. It spammed gigabytes of
> messages per day which ultimately crashed the system. There are some other
> challenges to solve, there's still too much code potentially leaking SQL
> connections or eternally spawning new sessions with each request. I will
> get there. This is in parts normal calendar/tasks/notes/mail users usually
> don't install.
>
> We will get closer to actual user needs next time around. This time it was
> all about making development easier and more accessible to our core team.

Hi Ralf,

That is a lot of work!  Thank you.

Please let us know where the tip jar is!

And please also consider posting the update on Mastodon too.

Many thanks.

Simon B