Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Images of games not stored to persistent storage location #698

Open
hillsandales opened this issue Jan 21, 2025 · 4 comments
Open

Images of games not stored to persistent storage location #698

hillsandales opened this issue Jan 21, 2025 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@hillsandales
Copy link

I have mapped the containers /opt directory for assets per README instructions but the image files don’t get saved there. I can write a file to the directory inside the container and it’ll show up on my host file system so it seems docker compose is mapping the volume correctly, but the app doesn’t appear to use it for storing any assets like game jpgs. The db does revenge .jpg and the mqtt broker shows it there too but images don’t load on the webpage. Are the images only stored in mqtt database and not local to the file system?

@github-project-automation github-project-automation bot moved this to Needs Triage 🗃️ in Playnite-Web Jan 21, 2025
@andrew-codes
Copy link
Owner

Hi, thanks for the report. Playnite Web takes the game art and converts it to .webp image format immediately before saving the files to disk. However, if no files are being saved, then there must be an issue. I'll need some more information to help me troubleshoot. Please do the following:

Set the DEBUG environment variable to playnite-web/game-db-updater/handler/persistAssets and then try syncing. This will mute all terminal output except for those relating to the saving of game assets. Please report back with any errors that you encounter. Errors will read like 'Error processing topic ___" followed by the error itself.

Also, are you seeing any entries in the Mongo database's collection, GameAsset? My expectation is that there should be no entries in the collection. Can you confirm this?

@andrew-codes andrew-codes self-assigned this Jan 27, 2025
@andrew-codes andrew-codes added the bug Something isn't working label Jan 27, 2025
@andrew-codes
Copy link
Owner

Also, can you try the latest version? I noticed this problem on my install and noted it is no longer an issue when upgrading, dropping the database, and resyncing. Thanks!

@hillsandales
Copy link
Author

Hi, thanks for the report. Playnite Web takes the game art and converts it to .webp image format immediately before saving the files to disk. However, if no files are being saved, then there must be an issue. I'll need some more information to help me troubleshoot. Please do the following:

Set the DEBUG environment variable to playnite-web/game-db-updater/handler/persistAssets and then try syncing. This will mute all terminal output except for those relating to the saving of game assets. Please report back with any errors that you encounter. Errors will read like 'Error processing topic ___" followed by the error itself.

Also, are you seeing any entries in the Mongo database's collection, GameAsset? My expectation is that there should be no entries in the collection. Can you confirm this?

Yes, I have 932 items in the gameasset collection (seen by using Mongo Express).

I think I may have found the problem. In the container, I see the .webp images in /opt/playnite-web-app/src/public/assets/asset-by-id. (Note: It's storing inside the src/public/ assets/ directory, not the public/ assets/ directory.)

However, I have /opt/playnite-web-app/public/assets/asset-by-id mapped as the storage location for the assets within the container. I think /opt/playnite-web-app/public/assets/asset-by-id was mentioned in the docs as the storage location. Is storing the assets in the src/public/ directory intention or a bug?

I will change my container volume mapping if this is intentional.

@andrew-codes
Copy link
Owner

Ah I see. I think this is a typo in the docs. I'll leave this issue open to update the docs appropriately. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Needs Triage 🗃️
Development

No branches or pull requests

2 participants