deployment specific configuration
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 215
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
one thing we're trying to figure out is how to integrate stuff like taco-nginx nicely
the way you do it now is "start": "taco-nginx node app.js" in your apps package.json
but we dont wanna require package.jsons to have to have deployment specific stuff in them, so we are trying to think of the best way to 'insert' deployment commands like that in at build-time
one idea is to have a --start-prefix command for taco-build, e.g. taco-build "npm install--production" --start-prefix="taco-nginx"
another is a "taco" field in package.json that could have stuff like a start prefix, that way your 'npm start' doesnt need deployment specific stuff in it
thoughts?
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
Start by reading the issue's proposed package.json, taco-build, and taco-nginx integration approaches. Compare how deployment commands are currently supplied through the start script, then determine which configuration design the project should adopt and how completion would be validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100