MitocGroup / MitocGroup/deepify
Skip services provisioning on deepify deploy --frontend
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Now when executing deepify deploy ./ --frontend it runs provision step as well which is not really a frontend deploy. Find a way to take the existing .provisioning.json file to use for frontend config generation and deploy.
Contributor guide
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
Start at the deepify deploy command's frontend path and trace how provisioning currently runs. Inspect the existing .provisioning.json handling to determine how it can supply frontend configuration without provisioning services. Done means deepify deploy ./ --frontend skips provisioning while still generating frontend config and completing the deploy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100