[Task] Load and save manifest after the deployment of a build
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 6
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the deployment-ready handling and the deployment table, then trace how the manifest is currently loaded at environment startup. Done means the manifest is loaded when deployment is ready, saved in the deployment record, and reused from the database afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100