Proposal: Totem Initialization

sukrit007 commented 9 years ago

As a developer, it would save a lot of my time if:

I can get my new project initialized based on some seed generator with Dockerfile and optionally travis.
I can have all the webhooks initialized for my repositories (In progress)
I can get my totem config generated for my project and written to one of the providers (github, s3 , etcd etc)

Note:

We can make generators extensible and people can write their own generator if need be.
It should not be monolithic
Ideally we should be able to use one step (from generator) to invoke totem services and initialize the project.

Thoughts? , Ideas ?

sukrit007 commented 9 years ago

@jacobheun @jking90 @mmoulton Thoughts ? Ideas ? Please add your comments. Based on everyone's opinion , I can update the original ticket

sukrit007 commented 9 years ago

adding @kennedyj to loop.

10xLaCroixDrinker commented 9 years ago

@sukrit007 what is required for new totem projects?

10xLaCroixDrinker commented 9 years ago

Notes from meeting about this with @kennedyj @sukrit007 @mmoulton @rdpacheco

separate command line tool totem-cli: dev friendly util for interacting with totem
totem logs, totem list, deploy, undeploy
generators not tied to totem: yo {{something}} && totem init
totem init should only care about totem's ecosystem
.totemrc in home dir
published to npm

`totem init`

followed by a few questions to generate project
add dockerignore and append to gitignore if it exists
add totem.yml friendly to selected language (wizard)
either prompt for language or pass option
friendly to run multiple times to re-run wizard and update config (separate command?)
prompt to generate based on common parent config
can this programmatically run yeoman?
- run different genereators per lang