Hi Lee, > Kei, it's simply common sense, without posting here "hey, lads this is on SO > too" there's a chance we waste our time helping when you already had the > solution,
You are absolutely right. That thought simply did not occur to me. I would like to think that if i had this resolved at SO, i would post a reply here saying that i got it resolved in SO. Of course, i can see that from your point of view, you would never know for sure that i would do so. I understand where you are coming from. > First - and commented often in the list, logging into the server as yourself > (or deploy) does not mimic the environment in which capistrano runs, you can > mimic this by using inline ssh commands: > > ssh dep...@myserver 'whoami' > I am not familiar with linux environments and ssh. I do want to learn of course. To get me on the same wavelength as you, let me first describe how i ssh into my server from my development machine. ssh -i some_secret_key.pem [email protected] southeast-1.compute.amazonaws.com so when i access the server, i am inside as theusername. rafael aka leptom has suggested to me that i have the following in my deploy.rb which i did have. ssh_options[:username] = 'theusername' ssh_options[:forward_agent] = true ssh_options[:keys] = %w( /home/theusername/.ssh/ida_rsa ) in other words for deployment, i am using the same user account as the one that is generally used for administering the server. Not sure if that is good from a security POV. Please let me know if I should create another user account on the server just for deployment. so back to your command ssh dep...@myserver 'whoami' so you are saying that i should login to my server from my devt machine using the following situation: ssh theusern...@ec2-123-45-678-90.ap-southeast-1.compute.amazonaws.com 'whoami' i have tried the following: ssh -i some_secret_key.pem [email protected] southeast-1.compute.amazonaws.com 'whoami' i get theusername ssh theusern...@ec2-123-45-678-90.ap-southeast-1.compute.amazonaws.com 'whoami' i get Permission denied. > Beyond that, I would assume the problem is that you don't have the same > permissions on production, and staging environment directories (something > :setup probably won't take care of for you) > I have made my staging folder chown to theusername:theusername already. > Additional you should verify that git doesn't have the auth credentials > cached… it can sometimes help to erase the Git cache and start over. I do not understand this. What does it mean to erase the Git cache? I have googled and apparently the command is git reset --hard Do i do this in the server's staging folder or my own devt machine? > If you still have problems - I'd be more than happy to have 15 minutes with > you on IRC later, then as a last resort, maybe you can let me poke around on > the server with your supervision, and we can find out what's going wrong. I will be more than happy to have your assistance! I am in UTC +8 will be online from 9am - 1pm that would be New York time 9pm - 1am i will also be online after that. cannot be sure about the exact timing. What IRC nick do i look out for? My IRC nick is Zeu5. Thank you! -- * You received this message because you are subscribed to the Google Groups "Capistrano" group. * To post to this group, send email to [email protected] * To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/capistrano?hl=en
