automate digital ocean provisioning
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 215
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
this is a continuation of the discussion here https://github.com/maxogden/taco/issues/2#issuecomment-32710628
@klaemo it would indeed be awesome to create a new droplet and install taco on to it, 100% automated. I think the best route there is to go through https://npmjs.org/package/santa. It may also be possible to create a digital ocean image with taco pre-loaded, but I would be weary of that approach if it means having to update the image all the time. One of the nice parts about the current approach taco takes is that it gets the newest version of everything when you install it.
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 with the discussion linked from issue #2 and the santa npm package mentioned here to recover the intended provisioning flow. Done should mean a fully automated DigitalOcean droplet creation and Taco installation path, but this issue does not identify repository entry points or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100