PgAdmin and MongoExpress Containers Not Visible on Azure Deployment (Aspire Hosting) #8989
Unanswered
man-jadeja
asked this question in
Q&A
Replies: 1 comment 2 replies
-
Those are development time resources only. We can consider making it possible to deploy them but right now they are unsecured by default and left out of publishing. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team,
CC : @goldytech
I’m currently deploying my Aspire-based project to Azure. Locally, everything works fine — I can see and access the PgAdmin and MongoExpress UI containers. Here is how I’ve set them up:
`// Postgres with PgAdmin
var pgsPassword = builder.AddParameter("pgs-password", secret: true);
var postgres = builder.AddPostgres("postgres", password: pgsPassword)
.WithPgAdmin()
.WithLifetime(ContainerLifetime.Persistent);
// Postgres database
var postgresdb = postgres.AddDatabase("supplierenginedb");
// MongoDB with MongoExpress
var mongo = builder.AddMongoDB("mongo")
.WithMongoExpress()
.WithLifetime(ContainerLifetime.Persistent)
.WithDataVolume();
`
However, after deploying to Azure, these PgAdmin and MongoExpress containers are not visible in the Aspire Dashboard or Azure resources. I've attached screenshots comparing my local environment (where they are visible) and Azure (where they are missing).
I'm wondering: Am I missing any configuration to ensure these UI containers are deployed to Azure? Is there a setting required in Azure for these to appear properly? Or are management UIs like PgAdmin and MongoExpress handled differently on Azure for security or configuration reasons? Any guidance would be much appreciated!
Thanks a lot!
Beta Was this translation helpful? Give feedback.
All reactions