I have mistakenly deleted my app that i have deployed on heroku. i have deleted both the local and the remote versions of the code.
I'd like to know how to restore it.
This is not possible I am afraid.
The Heroku Dashboard (in Settings) says "Deleting your app and its add-ons is irreversible".
The Command CLI provides the apps:destroy command but nothing to recover.
Related
I have associated my new app with the old one in the store, then when hitting Local Machine I get the message:
The app ____ is already installed on this machine.
if you continue with the current deployment , the existing app will be
uninstalled and the apps current state will be deleted.
are you sure you want to continue?"
I need to keep the local state folder as that's where I have saved user data in the first version of the app, I don't want my users losing data.
Does any one know of a way to achieve this ?
This will not happen for actual users of your application who download it from the Store. The issue here is that when debugged, the app is signed with a local certificate as opposed to the Store-signed version. If you want to debug this "update" scenario, the easiest way to do so is:
Checkout the older version of your app from Git
Run it with debugger
Add some data
Close the app
Checkout latest commit again
Run app
Today I made a change to my rails app, deployed it to Heroku, and everything seemed fine. But then, when I looked at the production website, my changes were not reflected. I ran heroku releases (and looked at their web dashboard version of this information) and indeed it shows my code should be there. It's pointing to the git commit that has my changed code in it as the one that was the most recent release.
Here's where it gets crazy: I use heroku run bash to get into the filesystem of my actual server, I use cat to view the changed file, and the new code isn't there! It's still the old version.
Has anyone seen this before? What else can I do to debug/fix this issue?
There is currently a large issue with Heroku that seems to be happening.
Their site: https://status.heroku.com/ seems to claim its only for Performance-L dynos. But if you search https://twitter.com/search?q=heroku&src=typd, you'll find convos about a lot of people not seeing the newest code deployed and/or having apps fully crashed.
I have deployed a node.js app in Bluemix using cf push. I have removed the start: entry from manifest.yml. In Bluemix I have set the environment variable BLUEMIX_APP_MGMT_ENABLEto devconsole+shell+inspector. This restages the app.
But when I open the App Manager by adding /bluemix-debug/manage/ I get a 404 error.
When I start Live Edit on the same project from DevOps Services I can open the App Manager. But I don't see what is different, it also seems to set the environment variable only.
What am I missing?
The Live Edit tool will automatically add 256MB to your application to facilitate execution of the additional features, which is likely why it is working with Live Edit.
Manually enabling the feature, however, will not automatically bump up the memory. Can you try adding some more memory to your application and restaging?
There are a couple of other limitations; refer to the Restrictions section on the App Management docs.
EDIT: Found issue in comments below. If command: node app.js is in manifest.yml, or if you are using -c with the CF CLI, it overrides the buildpack's ability to start the development utilities in App Mgmt. This happens even if you have the start command correctly specified in package.json or Procfile. To fix this, remove the manifest.yml entry, delete the application, and restage the application.
I've cloned an app (the app was made initially by someone else, they've added me as a collaborator as I took the job, but for more security, I've cloned the app myself by using the new clone feature) and renamed the new project, but it's still deploying to the old app, even though I've removed myself from its collaborators. I haven't changed anything on my computer and (presumably) because they have the same name, parse develop myappname and parse deploy [seemed to] work.
Just after I've posted the question, I've found the answer: it was the app key/master key pair. When I cloned the app, my app has been assigned new keys, but ~/config/global.json still had the keys of the old app. I've changed the app key and the master key in that file with the new keys in my Parse settings, and it worked. It's now deploying to my new app. Wish it updated automatically, though.
I've been experiencing this very odd problem lately in Heroku.
I develop and test locally, then I push the changes to Heroku. Even though the files pushed have been changed (and Heroku does recognize it and push the new files), when I look at the exact webpage on Heroku, it behaves as though it was still using the old version of the file that I just pushed.
When I see the HTML source in firebug, I can actually confirm that the old file is being used.
I've tried using git push -f to "force" the git push, but no luck
any ideas??
Try heroku restart to force a restart of all the dynos. I'm not positive but I've seen indications like this that they tend to "lazy restart" the dynos and workers after a push. If you want to guarantee all workers and dynos are working off the latest pushed code, do a restart after your push.
I know this is old, but I just recently had this problem, turned out it was just my cache. If you hit ctrl + F5 it hard refreshes the page and the cache. Worked in my case after searching everywhere.
Experienced same problem too, so checked the repo files by running heroku git:clone -a my-app cloned the files currently in heroku master, and confirmed that the files in repo are the updated version. Hence, the newer files are uploaded correctly but is not being reflected by heroku. Hence I ran heroku restart and waited a long time, like 3 or 4 hours, and problem solved, heroku started running the new files.
Not exactly sure if heroku restart or simply waiting for 4 hours solved the problem, and I doubt I needed to wait 4 hours for heroku to reflect newer repo.
However, I think, after deploying to the same master branch git push heroku master, heroku needs some time to reflect the newer files, hence the switch to newer files will not be instant, it takes time.
Hope this helps anyone else experiencing the same problem.