-
Notifications
You must be signed in to change notification settings - Fork 144
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
Documentation screenshots out of date #300
Comments
Hi @WeThePeopleMI, thanks for reaching out! Sorry to hear you're having issues setting up Library. If you're getting a |
Hi @WeThePeopleMI, you can find logs by clicking into your app, using the More menu, and clicking "view logs". Any logs (especially errors) would be very helpful! |
Andrew, I just opened the app again, and now the log is running and updating, so ignore my last comment. I'll post the full log (with our stuff covered over) in a bit. Sorry about that. Didn't realize. Best, Sargeant |
Andrew, I figured it out (with the help of a colleague)! I'm sharing what we found here -- as it might relates to part of the getting started process no working for us. Not sure if the issue is generalized, or just our unique situation. When we opened the full logs, and searched for errors, we found this message repeated throughout. Pretty clear. In fact when I reconfigured the Heroku app two nights ago, I had written in my notes that our Google_Application_JSON included different items than the image in NYTimes wiki "Getting Started" process. Our Google_Application_Jason (before figuring out mistake): So I had already noted that the JSON items didn't include the same fields. My supervisor remembered that when we went through the setup process the "Create a Key" portion of the "Create a Service Account" instructions never came up for us in the Google Cloud Platform part of the process. It just wasn't an option. So we went back, and sure enough, under the "APIs and Services" section, there was no key configured. So we went ahead and configured the key, and were prompted to save the JSON. Now it looks like the one in the "Getting Started' portion of the wiki: I think what tripped us up:
But we're all good now. We went back and set up the key, replaced the Google_Application_JSON in the Heroku configuration, and our wiki loaded! Just thought I'd share in case its helpful for future users. Many thanks!!! Best, Sargeant |
Thanks for the update @WeThePeopleMI! Glad to have you up and running. Going to keep this open, as we're currently working on updating and refining our documentation. It looks like google has updated its interface since we've taken those screenshots, so we will need to update those. cc @hopefourie-nyt / @crystalnyt for later! |
Context (Environment)
I am deploying a pilot wiki from a folder on a personal google drive (before proposing we use a shared staff drive to create one)
Expected Behavior
Deploying my heroku app and seeing my wiki.
Actual Behavior
I received the"Uh oh, that's a 500." message. I've checked through all my work twice, read responses in the google group and here -- and still no luck.
I checked my the activity log and found this:
And I checked the error message for the page and found this:
And I can see reference to "personalizedhomepage" in the page's code but have no idea what to do with this information.
To Reproduce
NA
Additional Information
NA (none that I know of)
Possible Solution
See above.
Thank you! I'm so excited to get this to work, and trying my best to do whatever I can to make sense of the error messages on my own; I just hit a wall. Any help would be greatly appreciated.
Thank you again,
Sargeant Donovan-Smith
The text was updated successfully, but these errors were encountered: