Open mabdullahabid opened 3 years ago
Hi @mabdullahabid, in large it's left as an exercise for the developer to figure out how they want this to work in prod. I have one production project (30 daily users) that uses this and I use it the same as I do in development.
From an "official statement from the developer" point of view I mainly recommend that you configure the cache, so that you don't have your server reading the manifest.json
file every time someone goes to load an asset.
There are other considerations, like do you want your assets hosted on S3, for example. However, that is outside the scope of this package.
What would be the best practices for deploying this to production or would the same setup in installation work seamlessly across environments?