-
Notifications
You must be signed in to change notification settings - Fork 66
ease the setup #170
Comments
I like that idea! MyUSA setup is super annoying. anything to make setup easier would be fine for me! only consideration is that we should make sure we are still able to test auth functionality locally if we'd like (perhaps some type of env var to switch on) |
@afeld we are now using GitHub auth! I also updated the docs with instructions on how to set up auth: https://github.com/18F/dolores-landingham-bot/blob/master/CONTRIBUTING.md#authentication What do you think? |
Definitely better, though having watched people go through setup a couple times, taking out the auth setup step altogether would be a big friction-remover for contributing. |
Sorry, by "take out" I mean "make feature-flaggable for development". |
I'm thinking something like the following: [email protected] foreman start which would find or create that user and bypass OAuth. |
* allows a local developer to log-in; * bypasses oauth * see .sample.env * set developer email * set skip_team_check to 'true'
Hey team-
Having had used this project in a couple of open source workshops thus far, I've watched a bunch of people hit a lot of hurdles when trying to set up the app locally. In particular, setting up the MyUSA application and the Slack token are a bit of a nuisance. I was wondering: thoughts about feature-flagging those connections, where in development it could just post to the console or something, and have the user automatically logged in as a dummy admin user? Just thinking it could get people up and running a lot faster. Thoughts?
The text was updated successfully, but these errors were encountered: