fix: resolve 404 deployment issue by using relative base path#9
Merged
maruf-pfc merged 1 commit intoblackstart-labs:mainfrom Apr 5, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have filled out the Pull Request template for the fix in the fix/deploy-base-path branch:
Proposed Changes
Description
The deployment was failing with a blank white screen due to 404 errors for static assets. This was caused by the base path being hardcoded to /github-issue-tracker/, which was incorrect for the specific environment. Since the application uses Hash History, switching to a relative base path (./) ensures that the index.html correctly locates its assets regardless of the repository name or subdirectory.
Related Issues
Resolves the white screen deployment issue.