-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup Notes for Deployed Application #36
Conversation
Thanks for your PR. I had an improved getting started in my backlog for quite a while and came up with something. If you put yourself in your co-workers shoes, is this something they could work with? Or should we merge additional bits from your tutorial / docs? |
I think it would be good to include the permissions section as this has caused us issues in the past. Just remembered another thing: the columns |
A
This sounds like a good target for better validation (#39). I'll probably rather implement validation than putting that in to a distinct document. |
yeah that sounds like a good plan. Just another quick one for the validation. If you run |
Another one for a Users must configure the appropritate login callback url. |
This is not the case anymore. |
I've created the TROUBLESHOOTING document I've talked about: https://github.com/nikku/wuffle/blob/master/docs/TROUBLESHOOTING.md Along with the vastly improved startup validation this should give users enough hints to know where to continue. |
Note that your setup instructions are outdated: As of v0.16.0 specifying repositories is no longer necessary, you control repository apperance on the board entirely via GitHub app installation. |
Here are the detailed setup notes that I have created for my team including screenshots and examples