You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I first clone the project and run it using the .yaml file docker-compose-dev.yaml, everything works fine. However, a problem occurs when I use the command npm run build. After build success, I go to the domain http://localhost:80/view?m={mediaID}, and it doesn't work when I click on some media in the list.
To Reproduce
Steps to reproduce the issue: (i followed by Develop_docs.md )
Run docker-compose -f docker-compose-dev.yaml up
In the frontend folder, runnpm run build (or docker-compose -f docker-compose-dev.yaml exec frontend npm run dist)
Copy the contents of frontend/dist/static/ to the static/ folder in the root: cp -r frontend/dist/static/* static/
Restart the web service: docker-compose -f docker-compose-dev.yaml restart web
Go to http//localhost/user/{username} and choose a random media item in the "My Media" tab.
Observe the error below
Screenshots
Environment
OS: Ubuntu 22.04
Installation method: Docker
Browser: Chrome
The text was updated successfully, but these errors were encountered:
Describe the issue
When I first clone the project and run it using the
.yaml
filedocker-compose-dev.yaml
, everything works fine. However, a problem occurs when I use the commandnpm run build
. After build success, I go to the domainhttp://localhost:80/view?m={mediaID}
, and it doesn't work when I click on some media in the list.To Reproduce
Steps to reproduce the issue: (i followed by Develop_docs.md )
docker-compose -f docker-compose-dev.yaml up
frontend
folder, runnpm run build
(ordocker-compose -f docker-compose-dev.yaml exec frontend npm run dist
)frontend/dist/static/
to thestatic/
folder in the root:cp -r frontend/dist/static/* static/
docker-compose -f docker-compose-dev.yaml restart web
http//localhost/user/{username}
and choose a random media item in the "My Media" tab.Screenshots
Environment
The text was updated successfully, but these errors were encountered: