-
Notifications
You must be signed in to change notification settings - Fork 385
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
Private repo not working #39
Comments
I initially closed the issue, because i thought that it wasn't possible to proxy a private repo through to the application to update, but now i read that it should indeed be possible. So additionally to the problem above: Is it possible to use a private GitHub Repository with Hazel, without needing to own a server for a proxy? |
I tried to debug
Might be a problem with now rather than hazel. Hard to grasp what's going on, since the error is not very specific. I also tried to disable any firewall/anti-virus. |
I removed my comment because I actually succeeded, with a private repo. I use the workflow: My mistake was to include my username also in the repo name. Hence it appeared twice in the url. |
@onekiloparsec Yeah i think my problem is not related to the private repository since i also cannot deploy when using a public repository. |
I generated a token with private repo access. I am on a team that has access to our project. I was not able to deploy an update server following the workflow below, but my coworker was able to following the same steps. Sounds like a bug? Workflow: My error:
After a few seconds I am prompted for the passphrase to my ssh/id_rsa key. |
This issue resolve in my pull request #98 .
|
Not sure if the documenation is not accurate enough or i am doing something wrong, but i cannot get the setup to run properly.
This is my command:
now -e TOKEN=@github-token -e ACCOUNT="MyAccount" -e REPOSITORY="MyRespository" -e PORT="80" zeit/hazel
This is the message i get immediatly and i need to supply the password for my ssh file:
And this is the error i am getting after ~30 seconds:
What am i doing wrong?
The text was updated successfully, but these errors were encountered: