Re: Cloning the rollback?
Did you ever find any luck with this? I'm having the exact same problems as you right now... On Wednesday, January 30, 2013 6:16:36 PM UTC-6, Shahruk Khan wrote: Just wanna thank everyone for helping me out to this point so far. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
I ended up tweeting to Heroku and had the issue resolved within 2 - 3 days. Don't bother with support tickets, it takes about a week to hear a response. On Tue, Apr 23, 2013 at 10:33 PM, Nevin Watkins nevin.watk...@gmail.comwrote: Did you ever find any luck with this? I'm having the exact same problems as you right now... On Wednesday, January 30, 2013 6:16:36 PM UTC-6, Shahruk Khan wrote: Just wanna thank everyone for helping me out to this point so far. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to a topic in the Google Groups Heroku Community group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/heroku/bqHjUNN655M/unsubscribe?hl=en. To unsubscribe from this group and all its topics, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- Founder of BOX'NGO http://theboxngo.com/ View my LinkedIn Profilehttp://www.linkedin.com/pub/shahruk-khan/40/598/a40/ -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
Not clear what you tried exactly. Can you supply your git commands? On Tue, Jan 29, 2013 at 11:09 PM, Shahruk Khan shahruksem...@gmail.comwrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
I did a commit. Then, my computer hard drive crashed. I reinstalled my OS. I did git clone, but it gives me the files I had when I last committed, not the heroku rollback files. On Wed, Jan 30, 2013 at 10:21 AM, Jeff Schmitz jeffrey.j.schm...@gmail.comwrote: Not clear what you tried exactly. Can you supply your git commands? On Tue, Jan 29, 2013 at 11:09 PM, Shahruk Khan shahruksem...@gmail.comwrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
The clone command is relevant - what did you clone ? What do you mean by heroku rollback files? On Wed, Jan 30, 2013 at 9:30 AM, Shahruk Khan shahruksem...@gmail.comwrote: I did a commit. Then, my computer hard drive crashed. I reinstalled my OS. I did git clone, but it gives me the files I had when I last committed, not the heroku rollback files. On Wed, Jan 30, 2013 at 10:21 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: Not clear what you tried exactly. Can you supply your git commands? On Tue, Jan 29, 2013 at 11:09 PM, Shahruk Khan shahruksem...@gmail.comwrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
Shahruk Khan shahruksem...@gmail.com writes: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? If you type git log inside of your clone and look through the commits, do any of the earlier commit messages seem to match the version that you are looking for? If so, then you can type: git checkout d1fef46332865c232262bb0a3bc8ab935c9e8f06 (or whatever the commit number is) and your clone's files will be shifted over to that earlier version of your repository. Is that what you are asking for? -- Brandon Rhodes bran...@rhodesmill.org http://rhodesmill.org/brandon -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
Nope On Wed, Jan 30, 2013 at 11:04 AM, Brandon Rhodes bran...@rhodesmill.orgwrote: Shahruk Khan shahruksem...@gmail.com writes: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? If you type git log inside of your clone and look through the commits, do any of the earlier commit messages seem to match the version that you are looking for? If so, then you can type: git checkout d1fef46332865c232262bb0a3bc8ab935c9e8f06 (or whatever the commit number is) and your clone's files will be shifted over to that earlier version of your repository. Is that what you are asking for? -- Brandon Rhodes bran...@rhodesmill.org http://rhodesmill.org/brandon -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.comwrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
Let me explain this better. On my local copy, I did a git reset HEAD and pushed the changes to December 7th. I did a heroku rollback, then the OS reinstall. When I do a git clone, I get the files from December 7th and back. However, the heroku website has the version I want, which was from about a week ago. On Wed, Jan 30, 2013 at 11:14 AM, Shahruk Khan shahruksem...@gmail.comwrote: Nope On Wed, Jan 30, 2013 at 11:04 AM, Brandon Rhodes bran...@rhodesmill.orgwrote: Shahruk Khan shahruksem...@gmail.com writes: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? If you type git log inside of your clone and look through the commits, do any of the earlier commit messages seem to match the version that you are looking for? If so, then you can type: git checkout d1fef46332865c232262bb0a3bc8ab935c9e8f06 (or whatever the commit number is) and your clone's files will be shifted over to that earlier version of your repository. Is that what you are asking for? -- Brandon Rhodes bran...@rhodesmill.org http://rhodesmill.org/brandon -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
I essentially want to UNDO my git reseat HEAD. by the way I appreciate all of your help, thanks. On Wed, Jan 30, 2013 at 11:16 AM, Shahruk Khan shahruksem...@gmail.comwrote: Let me explain this better. On my local copy, I did a git reset HEAD and pushed the changes to December 7th. I did a heroku rollback, then the OS reinstall. When I do a git clone, I get the files from December 7th and back. However, the heroku website has the version I want, which was from about a week ago. On Wed, Jan 30, 2013 at 11:14 AM, Shahruk Khan shahruksem...@gmail.comwrote: Nope On Wed, Jan 30, 2013 at 11:04 AM, Brandon Rhodes bran...@rhodesmill.orgwrote: Shahruk Khan shahruksem...@gmail.com writes: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? If you type git log inside of your clone and look through the commits, do any of the earlier commit messages seem to match the version that you are looking for? If so, then you can type: git checkout d1fef46332865c232262bb0a3bc8ab935c9e8f06 (or whatever the commit number is) and your clone's files will be shifted over to that earlier version of your repository. Is that what you are asking for? -- Brandon Rhodes bran...@rhodesmill.org http://rhodesmill.org/brandon -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
When you clone from git you get not just the most recent version but all the history of the master branch. If you look in heroku releases you should see which of those commits correspond to which release. To check out that particular commit just use: $ git checkout ad3242 or whatever You'll probably want to create a branch at that point for ease of use, but that's up to you. -p On Wed, Jan 30, 2013 at 8:27 AM, Shahruk Khan shahruksem...@gmail.comwrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.comwrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.com wrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
How can I FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.com wrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.com wrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Cloning the rollback?
You can't FTP - that's not a feature Heroku supports. It sounds like you might want to spend a little bit of time familiarizing yourself better with Git. Once you get the hang of it, it's a much more powerful tool than FTP but it takes a little getting used to. Don't worry, though, your code should be safe and there in your git repo while you learn (try $ git log and you'll see all the history of your project) just make sure you don't push to that same Heroku app until you're confidant you have the right version of things. Best of luck, Peter On Wed, Jan 30, 2013 at 9:27 AM, Shahruk Khan shahruksem...@gmail.comwrote: How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.comwrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You
Re: Cloning the rollback?
All I see are the commits for December 7th and before. On Wed, Jan 30, 2013 at 12:38 PM, Peter van Hardenberg p...@heroku.comwrote: You can't FTP - that's not a feature Heroku supports. It sounds like you might want to spend a little bit of time familiarizing yourself better with Git. Once you get the hang of it, it's a much more powerful tool than FTP but it takes a little getting used to. Don't worry, though, your code should be safe and there in your git repo while you learn (try $ git log and you'll see all the history of your project) just make sure you don't push to that same Heroku app until you're confidant you have the right version of things. Best of luck, Peter On Wed, Jan 30, 2013 at 9:27 AM, Shahruk Khan shahruksem...@gmail.comwrote: How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.comwrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send
Re: Cloning the rollback?
Unknown revision or path not found in the working tree. On Wed, Jan 30, 2013 at 1:17 PM, Peter Keen peter.k...@bugsplat.infowrote: heroku rollback just rolls back to a previous release. It has nothing to do with git. Your git reset also did not generate a new commit, it just changed what the master branch pointed at. If you do heroku releases you should see the exact commit hash (i.e. Deploy 8fb3ce7) that was deployed, and the rollback will point at a previous release. To get to the state that is currently running on Heroku, find the commit hash that the currently-running release points at (it will say something like Rolled back to v88, so go to v88 and get the commit hash) and then git reset --hard your-commit-hash. On Wed, Jan 30, 2013 at 10:12 AM, Shahruk Khan shahruksem...@gmail.comwrote: All I see are the commits for December 7th and before. On Wed, Jan 30, 2013 at 12:38 PM, Peter van Hardenberg p...@heroku.comwrote: You can't FTP - that's not a feature Heroku supports. It sounds like you might want to spend a little bit of time familiarizing yourself better with Git. Once you get the hang of it, it's a much more powerful tool than FTP but it takes a little getting used to. Don't worry, though, your code should be safe and there in your git repo while you learn (try $ git log and you'll see all the history of your project) just make sure you don't push to that same Heroku app until you're confidant you have the right version of things. Best of luck, Peter On Wed, Jan 30, 2013 at 9:27 AM, Shahruk Khan shahruksem...@gmail.comwrote: How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.comwrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an
Re: Cloning the rollback?
Paste us the exact commands you used and the complete output you received. On Wed, Jan 30, 2013 at 10:35 AM, Shahruk Khan shahruksem...@gmail.comwrote: Unknown revision or path not found in the working tree. On Wed, Jan 30, 2013 at 1:17 PM, Peter Keen peter.k...@bugsplat.infowrote: heroku rollback just rolls back to a previous release. It has nothing to do with git. Your git reset also did not generate a new commit, it just changed what the master branch pointed at. If you do heroku releases you should see the exact commit hash (i.e. Deploy 8fb3ce7) that was deployed, and the rollback will point at a previous release. To get to the state that is currently running on Heroku, find the commit hash that the currently-running release points at (it will say something like Rolled back to v88, so go to v88 and get the commit hash) and then git reset --hard your-commit-hash. On Wed, Jan 30, 2013 at 10:12 AM, Shahruk Khan shahruksem...@gmail.comwrote: All I see are the commits for December 7th and before. On Wed, Jan 30, 2013 at 12:38 PM, Peter van Hardenberg p...@heroku.comwrote: You can't FTP - that's not a feature Heroku supports. It sounds like you might want to spend a little bit of time familiarizing yourself better with Git. Once you get the hang of it, it's a much more powerful tool than FTP but it takes a little getting used to. Don't worry, though, your code should be safe and there in your git repo while you learn (try $ git log and you'll see all the history of your project) just make sure you don't push to that same Heroku app until you're confidant you have the right version of things. Best of luck, Peter On Wed, Jan 30, 2013 at 9:27 AM, Shahruk Khan shahruksem...@gmail.comwrote: How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.com wrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You
Re: Cloning the rollback?
heroku releases git reset --hard 8d4f84a On Wed, Jan 30, 2013 at 1:37 PM, Peter Keen peter.k...@bugsplat.infowrote: Paste us the exact commands you used and the complete output you received. On Wed, Jan 30, 2013 at 10:35 AM, Shahruk Khan shahruksem...@gmail.comwrote: Unknown revision or path not found in the working tree. On Wed, Jan 30, 2013 at 1:17 PM, Peter Keen peter.k...@bugsplat.infowrote: heroku rollback just rolls back to a previous release. It has nothing to do with git. Your git reset also did not generate a new commit, it just changed what the master branch pointed at. If you do heroku releases you should see the exact commit hash (i.e. Deploy 8fb3ce7) that was deployed, and the rollback will point at a previous release. To get to the state that is currently running on Heroku, find the commit hash that the currently-running release points at (it will say something like Rolled back to v88, so go to v88 and get the commit hash) and then git reset --hard your-commit-hash. On Wed, Jan 30, 2013 at 10:12 AM, Shahruk Khan shahruksem...@gmail.comwrote: All I see are the commits for December 7th and before. On Wed, Jan 30, 2013 at 12:38 PM, Peter van Hardenberg p...@heroku.comwrote: You can't FTP - that's not a feature Heroku supports. It sounds like you might want to spend a little bit of time familiarizing yourself better with Git. Once you get the hang of it, it's a much more powerful tool than FTP but it takes a little getting used to. Don't worry, though, your code should be safe and there in your git repo while you learn (try $ git log and you'll see all the history of your project) just make sure you don't push to that same Heroku app until you're confidant you have the right version of things. Best of luck, Peter On Wed, Jan 30, 2013 at 9:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.com wrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to
Re: Cloning the rollback?
And the output, please, at least from heroku releases. On Wed, Jan 30, 2013 at 10:38 AM, Shahruk Khan shahruksem...@gmail.comwrote: heroku releases git reset --hard 8d4f84a On Wed, Jan 30, 2013 at 1:37 PM, Peter Keen peter.k...@bugsplat.infowrote: Paste us the exact commands you used and the complete output you received. On Wed, Jan 30, 2013 at 10:35 AM, Shahruk Khan shahruksem...@gmail.comwrote: Unknown revision or path not found in the working tree. On Wed, Jan 30, 2013 at 1:17 PM, Peter Keen peter.k...@bugsplat.infowrote: heroku rollback just rolls back to a previous release. It has nothing to do with git. Your git reset also did not generate a new commit, it just changed what the master branch pointed at. If you do heroku releases you should see the exact commit hash (i.e. Deploy 8fb3ce7) that was deployed, and the rollback will point at a previous release. To get to the state that is currently running on Heroku, find the commit hash that the currently-running release points at (it will say something like Rolled back to v88, so go to v88 and get the commit hash) and then git reset --hard your-commit-hash. On Wed, Jan 30, 2013 at 10:12 AM, Shahruk Khan shahruksem...@gmail.com wrote: All I see are the commits for December 7th and before. On Wed, Jan 30, 2013 at 12:38 PM, Peter van Hardenberg p...@heroku.com wrote: You can't FTP - that's not a feature Heroku supports. It sounds like you might want to spend a little bit of time familiarizing yourself better with Git. Once you get the hang of it, it's a much more powerful tool than FTP but it takes a little getting used to. Don't worry, though, your code should be safe and there in your git repo while you learn (try $ git log and you'll see all the history of your project) just make sure you don't push to that same Heroku app until you're confidant you have the right version of things. Best of luck, Peter On Wed, Jan 30, 2013 at 9:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.com wrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files back. When I do a commit, it only pulls the latest version of the website, not the rollback. How can I git clone the rollback off heroku? -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- You received
Re: Cloning the rollback?
v299 Rollback to v284 shahruksem...@gmail.com 2013/01/29 23:57:07 (~ 13h ago) v298 Rollback to v296 shahruksem...@gmail.com 2013/01/29 23:51:00 (~ 13h ago) v297 Rollback to v295 shahruksem...@gmail.com 2013/01/29 23:50:53 (~ 13h ago) v296 Rollback to v294 shahruksem...@gmail.com 2013/01/29 23:48:34 (~ 13h ago) v295 Deploy eb64161shahruksem...@gmail.com 2013/01/29 23:44:30 (~ 13h ago) v294 Deploy 9dec751shahruksem...@gmail.com 2013/01/29 23:41:30 (~ 13h ago) v293 Deploy 22773beshahruksem...@gmail.com 2013/01/29 23:40:39 (~ 14h ago) v292 Rollback to v290 shahruksem...@gmail.com 2013/01/29 23:32:24 (~ 14h ago) v291 Rollback to v289 shahruksem...@gmail.com 2013/01/29 23:31:40 (~ 14h ago) v290 Rollback to v288 shahruksem...@gmail.com 2013/01/29 23:28:51 (~ 14h ago) v289 Deploy 63e176eshahruksem...@gmail.com 2013/01/29 23:26:36 (~ 14h ago) v288 Deploy 2c16587shahruksem...@gmail.com 2013/01/29 23:22:12 (~ 14h ago) v287 Deploy fd32c1dshahruksem...@gmail.com 2013/01/29 23:17:18 (~ 14h ago) v286 Deploy 076e9bbshahruksem...@gmail.com 2013/01/29 23:14:08 (~ 14h ago) v285 Deploy 8d4f84ashahruksem...@gmail.com 2013/01/29 23:12:11 (~ 14h ago) On Wed, Jan 30, 2013 at 1:39 PM, Peter Keen peter.k...@bugsplat.infowrote: And the output, please, at least from heroku releases. On Wed, Jan 30, 2013 at 10:38 AM, Shahruk Khan shahruksem...@gmail.comwrote: heroku releases git reset --hard 8d4f84a On Wed, Jan 30, 2013 at 1:37 PM, Peter Keen peter.k...@bugsplat.infowrote: Paste us the exact commands you used and the complete output you received. On Wed, Jan 30, 2013 at 10:35 AM, Shahruk Khan shahruksem...@gmail.comwrote: Unknown revision or path not found in the working tree. On Wed, Jan 30, 2013 at 1:17 PM, Peter Keen peter.k...@bugsplat.infowrote: heroku rollback just rolls back to a previous release. It has nothing to do with git. Your git reset also did not generate a new commit, it just changed what the master branch pointed at. If you do heroku releases you should see the exact commit hash (i.e. Deploy 8fb3ce7) that was deployed, and the rollback will point at a previous release. To get to the state that is currently running on Heroku, find the commit hash that the currently-running release points at (it will say something like Rolled back to v88, so go to v88 and get the commit hash) and then git reset --hard your-commit-hash. On Wed, Jan 30, 2013 at 10:12 AM, Shahruk Khan shahruksem...@gmail.com wrote: All I see are the commits for December 7th and before. On Wed, Jan 30, 2013 at 12:38 PM, Peter van Hardenberg p...@heroku.com wrote: You can't FTP - that's not a feature Heroku supports. It sounds like you might want to spend a little bit of time familiarizing yourself better with Git. Once you get the hang of it, it's a much more powerful tool than FTP but it takes a little getting used to. Don't worry, though, your code should be safe and there in your git repo while you learn (try $ git log and you'll see all the history of your project) just make sure you don't push to that same Heroku app until you're confidant you have the right version of things. Best of luck, Peter On Wed, Jan 30, 2013 at 9:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous version of your master branch. jeff On Wed, Jan 30, 2013 at 9:36 AM, Shahruk Khan shahruksem...@gmail.com wrote: 1) git commit -m Blahblahblah git push 2) heroku rollback 3) OS reinstall 4) Git clone g...@heroku.com:app.git -- This does NOT clone the heroku rolled back version. On Wednesday, January 30, 2013 12:09:17 AM UTC-5, Shahruk Khan wrote: My hard drive crashed and I rolled my heroku files
Re: Cloning the rollback?
You're running the git commands inside the directory that you cloned from Heroku, correct? You should have said something like git clone g...@heroku.com:your-app-name.git, and then cd your-app-name. Then you should be able to say git show 8d4f84a and see the contents of that commit. Does that work? On Wed, Jan 30, 2013 at 10:41 AM, Shahruk Khan shahruksem...@gmail.comwrote: v299 Rollback to v284 shahruksem...@gmail.com 2013/01/29 23:57:07 (~ 13h ago) v298 Rollback to v296 shahruksem...@gmail.com 2013/01/29 23:51:00 (~ 13h ago) v297 Rollback to v295 shahruksem...@gmail.com 2013/01/29 23:50:53 (~ 13h ago) v296 Rollback to v294 shahruksem...@gmail.com 2013/01/29 23:48:34 (~ 13h ago) v295 Deploy eb64161shahruksem...@gmail.com 2013/01/29 23:44:30 (~ 13h ago) v294 Deploy 9dec751shahruksem...@gmail.com 2013/01/29 23:41:30 (~ 13h ago) v293 Deploy 22773beshahruksem...@gmail.com 2013/01/29 23:40:39 (~ 14h ago) v292 Rollback to v290 shahruksem...@gmail.com 2013/01/29 23:32:24 (~ 14h ago) v291 Rollback to v289 shahruksem...@gmail.com 2013/01/29 23:31:40 (~ 14h ago) v290 Rollback to v288 shahruksem...@gmail.com 2013/01/29 23:28:51 (~ 14h ago) v289 Deploy 63e176eshahruksem...@gmail.com 2013/01/29 23:26:36 (~ 14h ago) v288 Deploy 2c16587shahruksem...@gmail.com 2013/01/29 23:22:12 (~ 14h ago) v287 Deploy fd32c1dshahruksem...@gmail.com 2013/01/29 23:17:18 (~ 14h ago) v286 Deploy 076e9bbshahruksem...@gmail.com 2013/01/29 23:14:08 (~ 14h ago) v285 Deploy 8d4f84ashahruksem...@gmail.com 2013/01/29 23:12:11 (~ 14h ago) On Wed, Jan 30, 2013 at 1:39 PM, Peter Keen peter.k...@bugsplat.infowrote: And the output, please, at least from heroku releases. On Wed, Jan 30, 2013 at 10:38 AM, Shahruk Khan shahruksem...@gmail.comwrote: heroku releases git reset --hard 8d4f84a On Wed, Jan 30, 2013 at 1:37 PM, Peter Keen peter.k...@bugsplat.infowrote: Paste us the exact commands you used and the complete output you received. On Wed, Jan 30, 2013 at 10:35 AM, Shahruk Khan shahruksem...@gmail.com wrote: Unknown revision or path not found in the working tree. On Wed, Jan 30, 2013 at 1:17 PM, Peter Keen peter.k...@bugsplat.infowrote: heroku rollback just rolls back to a previous release. It has nothing to do with git. Your git reset also did not generate a new commit, it just changed what the master branch pointed at. If you do heroku releases you should see the exact commit hash (i.e. Deploy 8fb3ce7) that was deployed, and the rollback will point at a previous release. To get to the state that is currently running on Heroku, find the commit hash that the currently-running release points at (it will say something like Rolled back to v88, so go to v88 and get the commit hash) and then git reset --hard your-commit-hash. On Wed, Jan 30, 2013 at 10:12 AM, Shahruk Khan shahruksem...@gmail.com wrote: All I see are the commits for December 7th and before. On Wed, Jan 30, 2013 at 12:38 PM, Peter van Hardenberg p...@heroku.com wrote: You can't FTP - that's not a feature Heroku supports. It sounds like you might want to spend a little bit of time familiarizing yourself better with Git. Once you get the hang of it, it's a much more powerful tool than FTP but it takes a little getting used to. Don't worry, though, your code should be safe and there in your git repo while you learn (try $ git log and you'll see all the history of your project) just make sure you don't push to that same Heroku app until you're confidant you have the right version of things. Best of luck, Peter On Wed, Jan 30, 2013 at 9:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that is live on heroku right now. On Jan 30, 2013, at 11:16 AM, Jeff Schmitz jeffrey.j.schm...@gmail.com wrote: The heroku rollback is not a git command, and does not modify the repo from what I can tell. This does not have a thing to do with your OS reinstall I think. See http://stackoverflow.com/questions/9898286/heroku-rollback-didnt-update-the-head-remote-branch-did-it Heroku just deploys a previous
Re: Cloning the rollback?
Pretty weird. I would try cloning again from heroku and seeing if the commit shows up. On Wed, Jan 30, 2013 at 10:53 AM, Shahruk Khan shahruksem...@gmail.comwrote: $ git show 8d4f84a fatal: ambiguous argument '8d4f84a': unknown revision or path not in the working tree. Use '--' to separate paths from revisions On Wed, Jan 30, 2013 at 1:49 PM, Peter Keen peter.k...@bugsplat.infowrote: You're running the git commands inside the directory that you cloned from Heroku, correct? You should have said something like git clone g...@heroku.com:your-app-name.git, and then cd your-app-name. Then you should be able to say git show 8d4f84a and see the contents of that commit. Does that work? On Wed, Jan 30, 2013 at 10:41 AM, Shahruk Khan shahruksem...@gmail.comwrote: v299 Rollback to v284 shahruksem...@gmail.com 2013/01/29 23:57:07 (~ 13h ago) v298 Rollback to v296 shahruksem...@gmail.com 2013/01/29 23:51:00 (~ 13h ago) v297 Rollback to v295 shahruksem...@gmail.com 2013/01/29 23:50:53 (~ 13h ago) v296 Rollback to v294 shahruksem...@gmail.com 2013/01/29 23:48:34 (~ 13h ago) v295 Deploy eb64161shahruksem...@gmail.com 2013/01/29 23:44:30 (~ 13h ago) v294 Deploy 9dec751shahruksem...@gmail.com 2013/01/29 23:41:30 (~ 13h ago) v293 Deploy 22773beshahruksem...@gmail.com 2013/01/29 23:40:39 (~ 14h ago) v292 Rollback to v290 shahruksem...@gmail.com 2013/01/29 23:32:24 (~ 14h ago) v291 Rollback to v289 shahruksem...@gmail.com 2013/01/29 23:31:40 (~ 14h ago) v290 Rollback to v288 shahruksem...@gmail.com 2013/01/29 23:28:51 (~ 14h ago) v289 Deploy 63e176eshahruksem...@gmail.com 2013/01/29 23:26:36 (~ 14h ago) v288 Deploy 2c16587shahruksem...@gmail.com 2013/01/29 23:22:12 (~ 14h ago) v287 Deploy fd32c1dshahruksem...@gmail.com 2013/01/29 23:17:18 (~ 14h ago) v286 Deploy 076e9bbshahruksem...@gmail.com 2013/01/29 23:14:08 (~ 14h ago) v285 Deploy 8d4f84ashahruksem...@gmail.com 2013/01/29 23:12:11 (~ 14h ago) On Wed, Jan 30, 2013 at 1:39 PM, Peter Keen peter.k...@bugsplat.infowrote: And the output, please, at least from heroku releases. On Wed, Jan 30, 2013 at 10:38 AM, Shahruk Khan shahruksem...@gmail.com wrote: heroku releases git reset --hard 8d4f84a On Wed, Jan 30, 2013 at 1:37 PM, Peter Keen peter.k...@bugsplat.infowrote: Paste us the exact commands you used and the complete output you received. On Wed, Jan 30, 2013 at 10:35 AM, Shahruk Khan shahruksem...@gmail.com wrote: Unknown revision or path not found in the working tree. On Wed, Jan 30, 2013 at 1:17 PM, Peter Keen peter.k...@bugsplat.info wrote: heroku rollback just rolls back to a previous release. It has nothing to do with git. Your git reset also did not generate a new commit, it just changed what the master branch pointed at. If you do heroku releases you should see the exact commit hash (i.e. Deploy 8fb3ce7) that was deployed, and the rollback will point at a previous release. To get to the state that is currently running on Heroku, find the commit hash that the currently-running release points at (it will say something like Rolled back to v88, so go to v88 and get the commit hash) and then git reset --hard your-commit-hash. On Wed, Jan 30, 2013 at 10:12 AM, Shahruk Khan shahruksem...@gmail.com wrote: All I see are the commits for December 7th and before. On Wed, Jan 30, 2013 at 12:38 PM, Peter van Hardenberg p...@heroku.com wrote: You can't FTP - that's not a feature Heroku supports. It sounds like you might want to spend a little bit of time familiarizing yourself better with Git. Once you get the hang of it, it's a much more powerful tool than FTP but it takes a little getting used to. Don't worry, though, your code should be safe and there in your git repo while you learn (try $ git log and you'll see all the history of your project) just make sure you don't push to that same Heroku app until you're confidant you have the right version of things. Best of luck, Peter On Wed, Jan 30, 2013 at 9:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise get your code out again. Mark On Jan 30, 2013, at 8:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: Really all I want to do is clone the current slug that
Re: Cloning the rollback?
Yeah that's what I did. On Jan 30, 2013, at 2:05 PM, Peter Keen peter.k...@bugsplat.info wrote: Pretty weird. I would try cloning again from heroku and seeing if the commit shows up. On Wed, Jan 30, 2013 at 10:53 AM, Shahruk Khan shahruksem...@gmail.com wrote: $ git show 8d4f84a fatal: ambiguous argument '8d4f84a': unknown revision or path not in the working tree. Use '--' to separate paths from revisions On Wed, Jan 30, 2013 at 1:49 PM, Peter Keen peter.k...@bugsplat.info wrote: You're running the git commands inside the directory that you cloned from Heroku, correct? You should have said something like git clone g...@heroku.com:your-app-name.git, and then cd your-app-name. Then you should be able to say git show 8d4f84a and see the contents of that commit. Does that work? On Wed, Jan 30, 2013 at 10:41 AM, Shahruk Khan shahruksem...@gmail.com wrote: v299 Rollback to v284 shahruksem...@gmail.com 2013/01/29 23:57:07 (~ 13h ago) v298 Rollback to v296 shahruksem...@gmail.com 2013/01/29 23:51:00 (~ 13h ago) v297 Rollback to v295 shahruksem...@gmail.com 2013/01/29 23:50:53 (~ 13h ago) v296 Rollback to v294 shahruksem...@gmail.com 2013/01/29 23:48:34 (~ 13h ago) v295 Deploy eb64161shahruksem...@gmail.com 2013/01/29 23:44:30 (~ 13h ago) v294 Deploy 9dec751shahruksem...@gmail.com 2013/01/29 23:41:30 (~ 13h ago) v293 Deploy 22773beshahruksem...@gmail.com 2013/01/29 23:40:39 (~ 14h ago) v292 Rollback to v290 shahruksem...@gmail.com 2013/01/29 23:32:24 (~ 14h ago) v291 Rollback to v289 shahruksem...@gmail.com 2013/01/29 23:31:40 (~ 14h ago) v290 Rollback to v288 shahruksem...@gmail.com 2013/01/29 23:28:51 (~ 14h ago) v289 Deploy 63e176eshahruksem...@gmail.com 2013/01/29 23:26:36 (~ 14h ago) v288 Deploy 2c16587shahruksem...@gmail.com 2013/01/29 23:22:12 (~ 14h ago) v287 Deploy fd32c1dshahruksem...@gmail.com 2013/01/29 23:17:18 (~ 14h ago) v286 Deploy 076e9bbshahruksem...@gmail.com 2013/01/29 23:14:08 (~ 14h ago) v285 Deploy 8d4f84ashahruksem...@gmail.com 2013/01/29 23:12:11 (~ 14h ago) On Wed, Jan 30, 2013 at 1:39 PM, Peter Keen peter.k...@bugsplat.info wrote: And the output, please, at least from heroku releases. On Wed, Jan 30, 2013 at 10:38 AM, Shahruk Khan shahruksem...@gmail.com wrote: heroku releases git reset --hard 8d4f84a On Wed, Jan 30, 2013 at 1:37 PM, Peter Keen peter.k...@bugsplat.info wrote: Paste us the exact commands you used and the complete output you received. On Wed, Jan 30, 2013 at 10:35 AM, Shahruk Khan shahruksem...@gmail.com wrote: Unknown revision or path not found in the working tree. On Wed, Jan 30, 2013 at 1:17 PM, Peter Keen peter.k...@bugsplat.info wrote: heroku rollback just rolls back to a previous release. It has nothing to do with git. Your git reset also did not generate a new commit, it just changed what the master branch pointed at. If you do heroku releases you should see the exact commit hash (i.e. Deploy 8fb3ce7) that was deployed, and the rollback will point at a previous release. To get to the state that is currently running on Heroku, find the commit hash that the currently-running release points at (it will say something like Rolled back to v88, so go to v88 and get the commit hash) and then git reset --hard your-commit-hash. On Wed, Jan 30, 2013 at 10:12 AM, Shahruk Khan shahruksem...@gmail.com wrote: All I see are the commits for December 7th and before. On Wed, Jan 30, 2013 at 12:38 PM, Peter van Hardenberg p...@heroku.com wrote: You can't FTP - that's not a feature Heroku supports. It sounds like you might want to spend a little bit of time familiarizing yourself better with Git. Once you get the hang of it, it's a much more powerful tool than FTP but it takes a little getting used to. Don't worry, though, your code should be safe and there in your git repo while you learn (try $ git log and you'll see all the history of your project) just make sure you don't push to that same Heroku app until you're confidant you have the right version of things. Best of luck, Peter On Wed, Jan 30, 2013 at 9:27 AM, Shahruk Khan shahruksem...@gmail.com wrote: How do you FTP? On Jan 30, 2013, at 12:08 PM, Mark Pundsack m...@heroku.com wrote: The repo and the running app's slug are separate. When you rollback, you just point back to an old complied slug. Sounds like you might have force pushed to your repo which may have destroyed your recent changes. The code might still be in there, but the log history is hidden. But not all is lost. Try heroku run bash to get a shell running on your slug. All of your code will be there. I'm not positive, but you might even be able to run git commands and find the commit hash you're looking for. Worst case, you can at least FTP or otherwise
Re: Cloning the rollback?
Just wanna thank everyone for helping me out to this point so far. -- -- You received this message because you are subscribed to the Google Groups Heroku group. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en --- You received this message because you are subscribed to the Google Groups Heroku Community group. To unsubscribe from this group and stop receiving emails from it, send an email to heroku+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
