Decide on CircleCI template features #24
Description
We should come to a consensus on features that we want to support for our default default CircleCI v2 template.
Options include
- ruby
- mysql
- postgres
- redis
- yarn / node
- default end-to-end testing framework (cypress, teaspoon, or other)
- imagemagick
- ...more
Additional questions
- Do we want to support optional workflows?
- What is the easiest way to maintain this over time?
- How do we avoid conditional spaghetti code in our template?