browserify / browserify/wzrd.in
Deploy #133
- Dominant language
- JavaScript
- Stars
- 637
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
Right now, wzrd.in proper is running what's on the "production" branch, which has diverged significantly from master. We need to do this upgrade. Proposed steps:
- [ ] QA - Someone should point a requirebin instance at it and try out some common scenarios, so we're confident this will work
- [ ] Install docker on the box
- [ ] Install nvm on the box
- [ ] Install the new instance of wzrdin that runs against docker in parallel using node 6 in nvm
- [ ] Flip the port with nginx
- [ ] Tear down the old instance
If you want to help with this, you can either take on some of the QA work, or you can help flesh out the deploy plan. We would ideally want 2 or 3 of us and a weekend, I think.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the production and master branches, then review the proposed requirebin QA scenarios and deployment steps involving Docker, nvm with Node 6, and nginx. Done means the new wzrd.in instance passes QA, runs in parallel, traffic is switched, and the old instance is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript, nginx, node.js
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100