Azure-Samples/contoso-real-estate

[Chore] Blog assets (img) - 500 Internal Server Error

Open

#461 opened on Apr 9, 2024

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)JavaScript (534 forks)auto 404
good first issuescope: cmsscope: infra

Repository metrics

Stars
 (973 stars)
PR merge metrics
 (PR metrics pending)

Description

Are you accessing the project from the GitHub Codespaces?

  • No, I am running the project on my local machine (I will fill in the OS section below)
  • Yes, I am using GitHub Codespaces.

Note: The project is optimized to run on Codespaces. We welcome contributions to enhance it for cross-platform local development, but it's not something we will prioritize right now. Thank you!

Describe the bug Images for the blog app are unavailable - 500 Error

To Reproduce Steps to reproduce the behavior:

  1. Open the Codespace
  2. Type in command 'npm start'
  3. Open blog app
  4. See error

Expected behavior All assets should load successfully on the UI

Screenshots contoso-blog-assets-500

OS (please complete the following information):

  • OS:
  • OS Version:
  • npm version:
  • Node.js version:
  • output of azd version:

Additional context Add any other context about the problem here.

Contributor guide

Research direction
Investigate the static asset serving configuration for the blog app. Check the server logs for more details on the 500 error and verify the image file paths.
Tech stack
javascriptnodejs
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitNode.jsnpm
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70