TODO.org

Setup Recipe

Show Passenger as an option for production web server

Ask if we are deploying to Heroku

Do not show Passenger as an option if we are deploying to Heroku

Change development DB question to just ask about application DB?

Remove SQLite option

Add Compass to front-end framework options

Remove skeleton and normalize from options

Remove authorization question

Remove starter app question

Add Formtastic to form builder gems

look into creating formtastic-specific devise pages (views recipe)

Add new option to authentication - Devise + OmniAuth

Research the right options for email sending

Removed email option by setting it in defaults

Add koality

Remove WEBRick from production web server choices

Remove MongoDB from DB choices

Ask about ActiveAdmin

Fix diagnostics message at end of template

Remove assets logger noise by default

Look at robots.txt and possibly remove

Remove Github repo creation

Change color scheme for questions!

Ask about exception notification

(2h) Use user’s name by default for database username

Discover effective testing pattern for recipes

(2h) Create .ruby-version file

(8h) Add ability to give multiple answers

Use this for OmniAuth providers

Auto-create postgres user

Offer to cancel if DB already exists

Create mysql user in the gems recipe, similar to postgres

Split gems.rb into a bunch of smaller recipes.

Port magic scrolls from Relevance-Rails

Add deploy script for Heroku if deploying to Heroku (reference tilt:config/deploy script)

Ask about background jobs/Sidekiq?

Ask about task scheduling/Whenever

Rails version should use current Rails version pinned with ~.

Nix upfront recipe-chooser menu.

Problems to be solved

• Code not yet testable in clean, isolated way.
  • Stock layout.erb causes generator to run bundler at construction time, other state-changing things.
  • Testing requires shelling out to generate template, running afoul of user prompting.

Document

Opting out of a prompt via YAML “unless_recipe” means that question

will not run if the indicated recipe is present – even if that recipe itself is opted out of. This means if we want no frontend prompt to appear if the heroku recipe is an option, but do want the actual frontend recipe to run promptless, the heroku recipe will have to set the prefs object accordingly. Which means the frontend recipe must be marked to run after the heroku recipe so that it can respond to the settings defined in the heroku recipe.

Selection combos currently deemed worth covering.

[x] Done. [_] TODO [?] Requires multiple-select branch to be merged.

	(d) default	(d) conf.	(d) inv.	(oa) twitter	(oa) all
devise	x	x	x
omniauth				x	?
both	_	_	_		?