LibreDB Studio - one click service template (tested, branch ready)

[yusuf-gundogdu]

peaklabs-dev closed my earlier template PR, #10756, on 12 August with "we only accept service templates for projects with over 1,000 stars, so I'll be closing this one. If the service reaches that threshold, feel free to open a new PR." It is at 1,183 today: github.com/libredb/libredb-studio, MIT licensed, a self-hosted SQL IDE you run in a browser, with drivers for 27 database engines.

I cannot take him up on the new PR part, because pull request creation here is collaborators only now. That is the only reason this is a discussion.

I did not revive the old diff. Two things in it would have failed on a real install, and I only found them by deploying it.

• The image has node but no wget and no curl, so the wget healthcheck in feat(service): add LibreDB Studio template #10756 exits 127 on every probe and the service never leaves unhealthy. That holds for the tag the PR pinned, 0.9.27, and for current 0.18.2. The template now probes through node, the way honcho and triliumnext already probe through an interpreter.
• In production the app marks its session cookie Secure for any host that is not loopback, and it will not drop Secure on the word of x-forwarded-proto. On the generated sslip.io domain, which Coolify serves over plain HTTP, the login POST returns 200, the browser discards the cookie, and the visitor is back on the login page while the health probe stays green. The template sets AUTH_COOKIE_SECURE and defaults it to false, with a comment to flip it once a TLS domain is attached.

I tested on Coolify 4.4.6 instead of with Docker alone. generate:services accepts the file, the service deploys from the catalog and reaches healthy on its own, and the admin password, the user password and the 64 character JWT secret are all substituted. Through the proxy on the sslip.io domain the login cookie comes back with no Secure flag. Set AUTH_COOKIE_SECURE to true on that same plain-HTTP domain and the cookie comes back with Secure, which is the state that produces the loop.

Branch: yusuf-gundogdu/coolify, feat/libredb-studio-0.18.2. Two added files, one compose template and one svg, nothing else touched. I cut it from release/v4.5 because CONTRIBUTING sends features to release/v4.x, and I will retarget it wherever you want, since the signals disagree: the issue template says service code should target next, CONTRIBUTING says there is no next branch although next exists, and the merged service templates I found went to next, main and feat/services, the last of which is gone since #11217.

So the one question: do you want this in the catalog? If yes, tell me the branch and whether you would rather pull it yourself. If one click services are not taking new entries right now, say so and I will drop it. Knowing is more useful to me than guessing.

[nktnet1]

#10756 (comment) says to open a new PR once you've reached the threshold:

That looks to be the case now, so why not just open a new PR?

[Cinzya]

PRs are currently locked for collaborators / members of the Coolify team. So outside contributors currently can't open PRs.