Clustericious::Command::generate* should be folded into a single class.
The commands clustericious generate app and clustericious generate client should be marked as deprecatd.
clustericious generate should generate a standard server + client dist
clustericious generate --client should generate just the client
clustericious generate --app (or maybe --server) should generate just the app/server code
The --mm, --mb and --dzil should indicate using EUMM, MB or Dist::Zilla. The default should be EUMM.
eventually the --db option should integrate with Clustericious::Database.
If Clustericious::RouteBuilder::Dancer2 gains traction we can add a --dancer2 option.
To do this, the templates should be refactored into app, client, common and installer. This like t/01_use.t (for common) and t/client.t (for client, included in server + client dist) should work and make sense regardless of the combination used.
Clustericious::Command::generate*should be folded into a single class.clustericious generate appandclustericious generate clientshould be marked as deprecatd.clustericious generateshould generate a standard server + client distclustericious generate --clientshould generate just the clientclustericious generate --app(or maybe--server) should generate just the app/server code--mm,--mband--dzilshould indicate using EUMM, MB or Dist::Zilla. The default should be EUMM.--dboption should integrate withClustericious::Database.Clustericious::RouteBuilder::Dancer2gains traction we can add a--dancer2option.To do this, the templates should be refactored into
app,client,commonandinstaller. This liket/01_use.t(for common) and t/client.t (for client, included in server + client dist) should work and make sense regardless of the combination used.