BASE_URL issue

[sebastianvoss]

When using the docker image with parameter BASE_URL it seem to not work as expected. Accessing the path it results in an 404 error.

docker run -it -p 8000:80 -e BASE_URL=/test asyncapi/studio:0.16.0
# open http://localhost:8000/test will result in 404

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[sebastianvoss]

I checked with version 0.18.1 and it has the same issue.

[dlouzan]

Interestingly, on a k8s cluster, this was working for us properly until 0.18.1 with no issues, but the latest 1.0.0 version broke it, none of the images, js, nor css can be loaded on a subpath. Reverting to 0.18.1 fixed it for the time being.

Using docker with BASE_URL setting. I can see in the code that the build target was modified in 1.0.0 to use turbo vs craco earlier: v0.18.1...ui-v1.0.0

@fgreinacher

[fgreinacher]

Seems that https://github.com/asyncapi/studio/pull/688/files broke this.

Will provide a fix.

[asyncapi-bot]

🎉 This issue has been resolved in version @asyncapi/studio-v1.0.0 🎉

The release is available on:

• GitHub release
• @asyncapi/studio-v1.0.0

Your semantic-release bot 📦🚀

[sebastianvoss]

I think it is still an issue. I just tested it with:

docker run -it -p 8000:80 -e BASE_URL=/test asyncapi/studio:1.0.0

[KhudaDad414]

@fgreinacher I tried to find the issue but I can't find it. the BASE_URL_PLACEHOLDER is being set up correctly and the echo "find /usr/share/nginx/html/ -type f -print0 | xargs -0 sed -i \"s|${BASE_URL_PLACEHOLDER}|\${BASE_URL}|g\"" > $ENTRYPOINT_SCRIPT && chmod +x $ENTRYPOINT_SCRIPT also works fine. can you see what is wrong here? 🤔

[sebastianvoss]

Hi @fgreinacher and @KhudaDad414 Thanks for all your effort and the great project. Did you already had the chance to look into this further?

[KhudaDad414]

@sebastianvoss I will look into this.

[KhudaDad414]

@sebastianvoss I have tested it and it seems to be working fine.
when I run:
docker run -it -p 8000:80 asyncapi/studio
it works fine without any errors.

docker run -it -p 8000:80 -e BASE_URL=/a/custom/path asyncapi/studio
will give these errors for me which is expected since I am not hosting the static files there:

[sebastianvoss]

@KhudaDad414 Thanks for your feedback. You are right, I had a wrong understanding of the BASE_URL parameter. I thought it is something like a context path which results the artefacts are hosted on that path. I changed my setup to rewrite the URL from /a/custom/path asyncapi/studio to / before passing the traffic to studio and everything works now.

Thanks again for the clarification.