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

Production documentation? #40

Open
mabdullahabid opened this issue Feb 4, 2021 · 1 comment
Open

Production documentation? #40

mabdullahabid opened this issue Feb 4, 2021 · 1 comment

Comments

@mabdullahabid
Copy link

What would be the best practices for deploying this to production or would the same setup in installation work seamlessly across environments?

@rykener
Copy link
Owner

rykener commented Feb 12, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants