Caching audio files on client
How can I cache an audio file that's in the public asset folder so I don't have to keep making a request to the back end?
3 Replies
Hi @Juan. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
To cache an audio file that's in the public asset folder, you can use the browser's built-in caching mechanisms. When you place an asset in the
public directory at the root of your Wasp project, it will be served at the root path / during development and copied to the root of the dist directory as-is.
For example, if you have an audio file audio.mp3 in the public directory, and your app is hosted at <https://myapp.com,> it will be made available at <https://myapp.com/audio.mp3.>
You should always reference public assets using root absolute path. For example, public/audio.mp3 should be referenced in source code as /audio.mp3.
Please note that assets in the public directory cannot be imported from source code. They are meant to be accessed directly via their URL.
As for caching, the browser will automatically cache these files according to the cache headers sent by the server. You can control these headers in your server configuration. If you want to ensure that the audio file is cached for a longer period, you might need to adjust these headers.
For more information, you can refer to the Wasp documentation on static asset handling (https://wasp-lang.dev/docs/project/static-assets#the-public-directory).
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Juan, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@kapa.ai Can you show an example of how and where to update the headers in an Opensaas app?
Let me check the knowledge base for you. One moment! :books:
----------------------
I'm sorry, but the provided knowledge sources do not contain specific information or examples on how to update the headers in an OpenSaaS app. It's recommended to refer to the documentation of the server you are using for your OpenSaaS app, as the method to update headers can vary depending on the server.
For Node.js servers, you can typically use the
response.setHeader method to set headers. However, please refer to the specific documentation for the server you are using for accurate information.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Juan, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?