Initial setup (db, email, admin, etc)#681
Initial setup (db, email, admin, etc)#681knownasilya wants to merge 17 commits intoStrider-CD:masterfrom
Conversation
50bb35c to
eb4db73
Compare
|
@keyvanfatehi @niallo how should I save the config? Use |
|
I'd suggest DB On Saturday, February 21, 2015, Ilya Radchenko notifications@github.com
Niall O'Higgins |
|
@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. |
|
The only thing about a file is a stateless environment like docker. Need to So we'll need to make sure that people know that strider will need to save Provider configs would also be nice, yeah, since that's pretty much the Cheers. On Tuesday, February 24, 2015, Ilya Radchenko notifications@github.com
Niall O'Higgins |
|
Good point.. hum I guess the db might have to be used.. |
6796fac to
395c3cc
Compare
78a7f0b to
4e466df
Compare
|
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 |
|
Yeah that is a good idea, maybe we could just send them to the plugin manager right after setup. |
add setup module and controller with dependency and bootstrap the ui
72b20cd to
7eb4600
Compare
6b0e7b4 to
41a7127
Compare
WIP, don't merge.
Basically a rough start on an initial setup page if no users exist.
TODO