-
Notifications
You must be signed in to change notification settings - Fork 1
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
upgrade to Staticman v3 #1
Comments
This doesn't seem to work. I tried to specify the GITHUB_PRIVATE_KEY in one line with or without 2021-03-03T15:30:15.017381+00:00 app[web.1]: node:internal/crypto/sig:124 And when I specify the key in multiple lines (copied the .pem file as is), then I got 2021-03-03T15:35:00.270122+00:00 app[web.1]: /app/node_modules/@octokit/request/dist-node/index.js:66 I needed to remove the GITHUB_PRIVATE_KEY completely to make it work with v2 again. So I guess it doesn't recognize the format, but I did the same what I did for the RSA_PRIVATE_KEY and that seems to work. |
Oops I forgotten to mention the permissions needed for GitHub Apps in my guide. Here's the official one: https://staticman.net/docs/getting-started.html. |
I did that (+ Read for Metadata). |
That seems to be a back-end setup question. Staticman's GitHub repo's issues/discussions are a place for this kind of questions b/c you might get help from fellow Staticman users there. |
This is what I tried... |
No, still no success. I added the latest info to eduardoboucas/staticman#406 |
Ok, the key has to be set with newlines and I forgot to install the newly created app. Thanks again for your help @VincentTam ! |
💡 The official quick start guide says that authentication via GitHub App is preferred over the traditional GitHub bot: https://staticman.net/docs/getting-started.html
ℹ️ For the API setup, apart from Staticman's official site, you may
The text was updated successfully, but these errors were encountered: