Eric Deandrea

@agoncal Changes are in - please review. If all looks good, please **Squash and merge**.

I'm certainly not tied to angular. The only drawback I can see is that currently we only have a single container image for the ui. Doing this means we'd have...

@agoncal After learning a little bit more about Quinoa, it doesn't seem like its a replacement for the Angular - just a way to bring the Angular (or whatever SPA...

Would there be any downsides? The only one I can see is that we wouldn't be able to separate the UI as static content anymore. I'm not sure how important...

@cescoffier Are you building the UI in the workshops? Or just running it? If you're just running it, why not just `docker run -it quay.io/quarkus-super-heroes/ui-super-heroes:latest`? That would bring up the...

Ahhh I see - the workshop still has the UI bundled inside a Quarkus app, whereas the superheroes separated the UI into its own thing.

@agoncal / @cescoffier did we come to a decision on this? I'll summarize from above comments: ## Pros - Quinoa is new & cool - No more Node.js tooling required...

> The question could be: does it make sense to introduce Quinoa to an Angular project (without Quarkus)? I'm not sure what you mean? Quinoa is a Quarkus extension and...

@cescoffier / @agoncal coming back to this a few months later - are we all still feeling that things are better left as-is? If so, I will close out this...

See #133 - this will fix that. Until that gets merged if you want to fix it manually you can modify the script to change ``` VILLAINS_DB_CONNECT_STRING="jdbc:otel:postgresql://${VILLAINS_DB}.postgres.database.azure.com:5432/${VILLAINS_DB_SCHEMA}?ssl=true&sslmode=require" ```