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
Can't "just" push to remote repo #116
Comments
Are you sure you did everything correctly? You are not supposed to create any repos remotelly, it's |
Creating the repo manually was something I did after nothing seemed to work.
|
yeah, this is not right.. if you do it manually, dokku knows nothing about it.. so build process not initiated. please describe what you exactly doing, so I'll make sure it's correct :) |
As you know I'm trying to install a new server now. But it's gonna take a while :) |
Ensure you're pushing to |
Do I need to do anything with my default git user besides executing the gitreceive command? |
Nope. You need to make sure you upload keys though. On Thu, Jul 25, 2013 at 2:02 PM, webdevotion notifications@github.comwrote:
Jeff Lindsay |
What I see after Dokku has done it's business is:
Maybe I don't get how the git user is supposed to work. |
Are you using different keys for the git and the root user? AFAIK you can't use different ssh-keys on the same host without some magic. |
Nope. Same keys. |
git user has no password, it relies on keys. you should never be able to On Thu, Jul 25, 2013 at 2:09 PM, webdevotion notifications@github.comwrote:
Jeff Lindsay |
Ok thanks @progrium. I know where to look now. |
Great!
|
@asm89 Using the same public key for different users in the system won't cause any issues |
@rhy-jot I know, but from the initial story of @webdevotion I got the feeling he was using different keys for the root and git user. Anyway, glad it got solved! |
@rhy-jot Thanks for your suggestion:
For future reference:
|
--set-upstream was the only way I could get this to work as well. I'm using Vagrant on OSX. My settings:
Then did The documentation on setting the SSH keys needs a bit of padding out, I think. I can't understand why I have to do this. When I just use this:
I get this:
And, no password works. |
I'm getting this exact same error on Ubuntu 13.10 and 10.04 trying to follow the README example:
Note that the installation happened flawlessly as far as I can tell, and I can log in with the docker user via. ssh just fine:
What am I doing wrong? D: |
@christiangenco How did you setup your ssh keys ? |
Ahh that fixed it! I was using keychain.io like in Jeff's video without realizing Thank you! |
@plietar Thanks, you got me on the right track. I had added the public key manually to /home/dokku/.ssh/authorized_keys and then run the sshcommand acl-add (according to instructions here: https://www.digitalocean.com/community/questions/dokku-add-new-ssh-key), resulting in a file looking like:
But it was not working. To make it work, I had to remove the manually added ssh key so that the file looked like:
|
I think it would be helpful if the getting started in README made less assumptions about the installing user's knowledge. For instance... ssh command acl-add dokku progrium? what's dokku and what's progrium in this command? For me, and my knowledge... I couldn't discern if I was supposed to type that... I assume I'm supposed to replace "dokku" and "progrium" with my respective system's user? |
Also, on the Troubleshooting guide in the wiki that talks about the "fatal: 'NAME' does not appear to be a repository" it's making assumptions as to WHERE the changes need to be made... I do know that with passwordless ssh I generally need to copy the contents of id-rsa.pub to the server's authorized keys file... but is this something else? It really just doesn't explain it well for my knowledge of this in general I think. Not saying you have to change it... just my suggestion :-/ |
We should indeed use things like |
@motin I just solved this issue by removing every line that starts with |
I totaly agree with @joshuairl |
@kopax I too agree, the documentation for the current master branch is spread out across pull request comments or plain missing. Documentation-clarifying pull requests are very welcome, and do ask questions on Stackoverflow tagged Dokku, even if you already found the answer! :) Remember, Dokku is more a proof of concept than a tool to be used in production. That said, it can be worth using in production due to it's cheap initial price for smaller projects. In all cases it acts as a good testing ground to configure your app to support deployments through buildpacks. I can recommend reading up on how it works and taking some time to read the source code (there are not very many lines of code). Don't forget to add "export DOKKU_TRACE=1" to "/home/dokku/dokkurc" when troubleshooting. To get a Dokku host provisioned with specific versions of Dokku, Buildstep, Docker and some plugins, check out https://github.com/neam/dokku-host-provisioning. |
I created a Dokku (0.3.17) image on DigitalOcean running Ubuntu 14.04.2, and can access my server via ssh. I can't deploy the sample node-js app and get the same errors as listed by the @webdevotion, @christiangenco, and @motin.
@plietar I setup my SSH like this and can access the server via
What am I missing? |
I have the same problem with a Digital Ocean. I tried copy my local public key to the server with:
I am trying pushing with root(and dokku) too:
The file Any advice? |
Please open a new issue. |
Hello
Following the nice Vimeo screencast by @progrium I thought I would give Dokku another shot.
Installing goes smooth, but when I push my local Rails app to my server
I get:
When I manually create the repo on my server and push ( with success )
I don't get any of the Dokku magic like
app detected
etc.What am I missing here?
Thanks.
The text was updated successfully, but these errors were encountered: