Apicurio Studio compose with Postgresql as db server

[MicheleOdorizzi]

Hi all.
Does anyone have an example of compose file for deploying Apicurio Studio integrated with Postgresql in Podman?

Thank you very much.
M.

[EricWittmann]

What version of Studio are you trying to run? The latest version is 1.1 and it uses Apicurio Registry as the backend. The 1.0 version has its own backend, as does the 0.2 version. Studio is a little bit of a mess right now as we try to figure things out. The likely future direction is that we will simply incorporate the Studio functionality directly into Apicurio Registry.

[MicheleOdorizzi]

If possible, the latest version. Studio uses Registry as backend, and Registry could use Postgresql to store data, right?

[EricWittmann]

I don't have an example of that exact configuration, but I'll try to put one together this week if I have time. We have docker compose examples here:

https://github.com/Apicurio/apicurio-studio/blob/main/distro/docker-compose/in-memory-with-auth/docker-compose.yml

And some more here:

https://github.com/Apicurio/apicurio-registry/tree/main/distro/docker-compose

But none of those are using postgresql. It's not hard to add PG config though. I've got a few other things on my todo list first. :)

[MicheleOdorizzi]

Thak you very much.

I have used the in-memory-no-auth version, I have tried to add postgres, but I don't know Apicurio deeply to apply the correct changes in my compose.

[EricWittmann]

OK I've added a postgresql storage variant to the Apicurio Registry docker compose examples. You can find it here:

https://github.com/Apicurio/apicurio-registry/blob/main/distro/docker-compose/pg-no-auth/docker-compose.yml

Hopefully you can layer Studio 1.1 on top of that by using other examples.

Reminder: Registry 3.1 will have the Studio UI automatically included as part of the Registry UI, at which time the Studio project will likely be deprecated.