We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To be sure that an app is well deployed and usable, the app manifest should be loaded after the deployment is ready.
To manage cache on the manifest and avoid loading it each time, the result should be saved in the database.
Load the manifest when app is ready after the deployment and save the manifest in the deployment table.
Stop loading the manifest at every environment start but get it from the database.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What should be done
To be sure that an app is well deployed and usable, the app manifest should be loaded after the deployment is ready.
To manage cache on the manifest and avoid loading it each time, the result should be saved in the database.
Technical recommandation
Load the manifest when app is ready after the deployment and save the manifest in the deployment table.
Ecological concerns
Stop loading the manifest at every environment start but get it from the database.
The text was updated successfully, but these errors were encountered: