SShortSingh.
Back to feed

Developer details three Azure deployment methods for Dockerized Node.js app

0
·1 views

A developer built a Notes application using Node.js, Express, and PostgreSQL and packaged it with Docker. They deployed the same container image using three distinct methods on Microsoft Azure: Azure App Service with a managed PostgreSQL database, an Azure Virtual Machine running Docker Compose, and locally with Docker Compose for comparison. The process involved troubleshooting configuration errors, particularly around SSL settings required for Azure's managed database service. The developer documented the challenges and learning outcomes from each deployment approach to illustrate different cloud infrastructure models.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

AI-built Shopify app approved after 16-day review delayed by video requirement

An AI agent built and submitted the Sizecurve Shopify app on September 13, 2026. The app, which analyzes inventory data, faced a 16-day review process concluding on September 29. The primary delay resulted from Shopify requiring a configuration screencast video, which the AI could not produce without human assistance. The review's longest obstacle was creating a two-minute demonstration video, not technical or security issues. The app is now live with subscription pricing after approval.

0
ProgrammingDEV Community ·

Microsoft details how Azure AD SSPR abuse led to Kubernetes credential theft

Microsoft reported in September 2026 that a threat actor known as Storm-3068 compromised a single Azure AD account. The attacker achieved this by abusing the self-service password reset feature after obtaining account recovery details. Using the compromised identity, they then moved through Azure DevOps pipelines to steal credentials for Kubernetes clusters. This allowed access to over 50 downstream resources without exploiting a software vulnerability. The incident highlights risks from overly broad permissions and the abuse of legitimate system features.

0
ProgrammingDEV Community ·

Hiring developers remains challenging despite large talent pool availability.

The hiring challenge for developers has shifted from finding talent to identifying the right candidate for a specific job. Relying solely on skills lists or years of experience provides weak signals and can be misleading about a candidate's actual capabilities. Portfolios often fail to reveal the individual's specific contributions or problem-solving process. Effective hiring requires assessing communication skills and contextual fit, not just technical qualifications.

0
ProgrammingDEV Community ·

Node.js report design: choosing between repository HTML and stored PDF templates

A signed monthly property report requires an immutable evidence chain for later audits. The choice between storing layout as repository HTML or as a stored PDF template depends on team workflow and release authority. Repository HTML suits engineering teams who control changes through code reviews and deployments. A stored PDF template is better when compliance or document operations teams must approve field layouts independently of application releases. The essential requirement is naming a single layout owner and binding an immutable revision to the final signed document.

Developer details three Azure deployment methods for Dockerized Node.js app · ShortSingh