Staticman Instance gives 'Internal Server Error'

[sachin10101998]

I tried hosting my own instance of Staticman on Heroku. I cloned the repo, added the Github access token, Private RSA Key and hosted it as heroku app.
It's currently being run at https://staticmanaima.herokuapp.com
When I visit the site, it gave 'Hello from Staticman version 3.0.0!
Then I added the account from which I had taken the GitHub access token and added it in collaborators of my main repo but when I try to connect it through
https://staticmanaima.herokuapp.com/v2/connect/sachin10101998/aima-exercises/ it gives 'Internal Server Error'
Has someone faced this issue before? Any help would be greatly appreciated.

[VincentTam]

Hi, it would be better if you provide more info about your instance.

1. What was the commit at which Staticman was deployed? Different versions of Staticman can behave differently, so it's better to make it clear.
2. It seems that you're using v2, so what is the associated GitHub bot? We can't see it from the collaborators of your aforementioned GitHub repo. When we try to reproduce this error, we need to invite your bot as a collaborator, so it's important that you provide us the user name of your bot.
3. Are you aware of GitHub legacy token authentication is broken #283, in which users report some broken legacy features? Revert "Add support for GitHub Apps" #285 might solve your problem.
4. Have you added support for Akismet and/or Mailgun? It would be better for us to know that for replicating the error.

[sachin10101998]

@VincentTam

1. I haven't added staticman.yml files to my repo yet. I use staticman v2. I cloned the Staticman repo, set up the config.development.json file and pushed it to heroku by adding github access token from @staticmanaima github account.
2. I invited @staticmanaima from my main account as collaborator and tried to accept the invite by visiting that url which I mentioned in the first place i.e https://staticmanaima.herokuapp.com/v2/connect/sachin10101998/aima-exercises/
3. Revert "Add support for GitHub Apps" #285 hasn't been merged. should I make these changes in my clone to make it work?
4. No, I havn't added that.

[VincentTam]

Thanks for your response. For my first question, I mean, the Git SHA1 hash of the HEAD of your remote branch heroku/master. For example, my bot @staticmanlab was at 8eb6c32 last week. Others can compare this with the HEAD of the dev branch: https://github.com/eduardoboucas/staticman/compare/dev..VincentTam:deploy, so that we know which version you are using, and what you have modified. You may issue the following command to obtain such info.

git rev-parse heroku/master

[sachin10101998]

I believe I have something misconfigured. When I tried to add staticmanlab as a collaborator and accepted the invite using https://usinginstanceurl/v2/connect/my-username/myrepo , It worked perfectly returning an OK.
Issuing the above stated command gave me this bec497b18e89d769eba0c204be120501df27eaac

[VincentTam]

Your bot @staticmanaima takes the role of "developer" in each project to which it has write access. It shouldn't own any project. That's why we need these API token to restrict the bot's access. I should have asked for the output of

git diff upstream/dev..heroku/master

instead. The upstream here means this repo: https://github.com/eduardoboucas/staticman.git. You may change it to origin if you've directly cloned it. Anyways, my question is what exactly you've changed. Note that the SHA1 hash bec497b1 above doesn't match any commits in this repo and in your fork.

---

I had read your first reply slowly, now I've almost got it. You've edited config.development.json, so what exactly is this file? As a non-developer, I spent several days to get right the API config with Heroku last year. I've never succeeded with NODE_ENV: development. I always deploy to Heroku with production instead. Anyways, it would be clearer if you provide us the exact technical details.

[sachin10101998]

I made another instance of staticman and made the following changes:

1. Created a Procfile with web: npm start inside it.
2. Created a config.production.json file with the following contents.

{
    "gitlabToken": process.env.GITLAB_TOKEN,
    "githubToken": process.env.GITHUB_TOKEN,
    "rsaPrivateKey": JSON.stringify(process.env.RSA_PRIVATE_KEY)
  }

3. Added !config.production.json to gitignore file
4. Created a private RSA key for use with the API: openssl genrsa -out key.pem and then set heroku config variables.

$heroku config:set NODE_ENV="production" 
$heroku config:set RSA_PRIVATE_KEY="$(cat key.pem)" 
$heroku config:set GITHUB_TOKEN="My Token"

Then i just heroku create new app and pushed it there.
I made no changes in the staticman-key.pub file and it's same as it is in the original Staticman repo.

[VincentTam]

OK. I got it finally from your repo. My mind blocked me. You're working on top of 4e2f33b. After #243, it's reported that legacy authentication has broken in #283. You may try #285 to rollback Staticman v3's use of GitHub App.

[sachin10101998]

Is there any other way around?
If not, how do I Merge a pr which hasn't been merged upstream as in this case #285 in my fork of the repo.

[VincentTam]

See the first two commands in this Stack Overflow answer: https://stackoverflow.com/a/28954238/3184351

Git, designed by Linus Torvalds, is a tool for testing stuff, so it's sensible to learn how to git merge new stuff that hasn't been merged into the official repo.

[sachin10101998]

Am still unable to get it running.
What changes do I need to make in staticman-key.pub file?

[VincentTam]

What changes do I need to make in staticman-key.pub file?

That file is irrelevant. I've tested that myself with my instance. It seems that 4eb5ce2 is breaking the legacy support.

[sachin10101998]

How come @staticmanlab is not affected by it and is running perfectly?

[VincentTam]

staticman-key.pub is for display only. It doesn't affect the functioning of the app. Btw, the README is incorrect due to #256.

[sachin10101998]

No, I meant that if you try to build a staticmanlab2 version , will #283 cause problems?

[VincentTam]

I dunno. I've chosen PR 231, which doesn't work with 4eb5ce2 or 9ce2c48. So I won't merge PR 283. You may test and tell us the results.