Initial setup (db, email, admin, etc)

[knownasilya]

WIP, don't merge.

Basically a rough start on an initial setup page if no users exist.

TODO

• [x] Integrate https://github.com/mgonto/angular-wizard
• [x] Hookup form data to controller
• [x] Add an endpoint for processing a setup request
• [x] Save some of the settings in a config file
• [x] Figure out which settings need to be there
  • [x] Add proxy settings
• [ ] Cleanup existing config init

[knownasilya]

@keyvanfatehi @niallo how should I save the config? Use .striderrc (from the rc package), or store it in the db as the default config but over writable?

[niallo]

I'd suggest DB

On Saturday, February 21, 2015, Ilya Radchenko [email protected] wrote:

@keyvanfatehi https://github.com/keyvanfatehi @niallo https://github.com/niallo how should I save the config? Use .striderrc (from the rc package), or store it in the db as the default config but over writable?

— Reply to this email directly or view it on GitHub https://github.com/Strider-CD/strider/pull/681#issuecomment-75391415.

Niall O'Higgins W: http://niallohiggins.com E: [email protected] T: @niallohiggins

[knownasilya]

@niallo I went with the config, since there is only one config and it's not associated with the user. I think it would be a waste to put it in the db. Also it would be much easier to tweak if needed.

Just wondering what configs should be here, currently I have the smtp, admin user, and server_name. I'm thinking maybe adding provider config as well, so github, bitbucket, heroku, etc.

[niallo]

The only thing about a file is a stateless environment like docker. Need to make sure that state is saved properly, or people will be really confused. Folks likely already have their DB set up to persist, but may not for strider itself.

So we'll need to make sure that people know that strider will need to save $HOME/.striderrc

Provider configs would also be nice, yeah, since that's pretty much the first thing you need to set up.

Cheers.

On Tuesday, February 24, 2015, Ilya Radchenko [email protected] wrote:

@niallo https://github.com/niallo I went with the config, since there is only one config and it's not associated with the user. I think it would be a waste to put it in the db. Also it would be much easier to tweak if needed.

Just wondering what configs should be here, currently I have the smtp, admin user, and server_name. U'm thinking maybe adding provider config as well, so github, bitbucket, heroku

— Reply to this email directly or view it on GitHub https://github.com/Strider-CD/strider/pull/681#issuecomment-75763476.

Niall O'Higgins W: http://niallohiggins.com E: [email protected] T: @niallohiggins

[knownasilya]

Good point.. hum I guess the db might have to be used..

[oliversalzburg]

I'm not sure if it's too early to mention this, but I think it would be great if only the bare minimum of strider plugins are declared in package.json and, during the setup phase, the user can chose which plugins he wants.

[knownasilya]

Yeah that is a good idea, maybe we could just send them to the plugin manager right after setup.