I have a problem with my app when I uploaded it on heroku, I used the rollback to go back to a previous version without errors and it seems to be fine when I give it open app.
However, the code in pycharm shows the same errors, and if I commit, I get the errors of the latest version as if the code does not have the previous version, can I do something to recover that code?
You can just rollback to whatever previous version you like and then use
heroku git:clone -a APP-NAME
to get your code back.
Related
I tried to deploy my django application to heroku using the starter guide and the other manual that shows you to create your runtime, requirements, procfiles, installing django-heroku, etc. So I've now deployed my site but recieve the following error.My error I'm unsure of why this error is showing up at all especially when it worked perfectly fine locally. I haven't followed all of the django deployment checklist yet, such as setting DEBUG to False because I'd like to ensure that it works correctly before I do. If anyone could help me, that'd be much appreceiated!
You have to do migration after pushing to Heroku.
Note: Don't use local migrations. You can use Heroku bash to connect remotely and perform migrations just like you do locally.
I've created a basic Django app and I wanted to deploy it with Heroku. I have followed all the instructions given on Heroku but there was one error I made which was naming the file "procfile" instead of "Procfile". Now the website has been deployed but it only opens up to an application error. Upon checking the log, I have found the error code to be H14. I have since renamed the "procfile" to "Procfile" but the change doesnt seem to be integrated. How do I fix this?
Add the change on your repository, commit it, and push the applicable branch to Heroku. Finally, try to run Heroku again.
My Heroku Toolbelt is stuck updating.
When I run heroku in a console it says
Heroku Toolbelt is currently updating.
I have tried to uninstall and re-install but still the same issue.
I also tried to remove it with revo uninstaller.
Any ideas on how to fix?
Instead of completely uninstalling and reinstalling, I deleted a file called "updating" in "C:\Users\Profile-name\.heroku" and it started responding to commands again
I had the same issue with the older buggy Heroku toolbelt version. Except my heroku commands were not running from local but from Semaphore as a sequence of deploy steps.
Just running a update command first thing seems to solve the issue. Of this helps with your local toolbelt as well.
heroku update
The 5 minute update by heroku can be bypassed by removing the background_update! line from updater.rb or updating the toolbelt to version 3.15.2. That version will only lock if there really is an update instead of every 5 minutes.
Uninstall Toolbelt.
Manually delete
C:\Program Files (x86)\Heroku
C:\Users\Profile-name\ .heroku
Re-install toolbelt.
As of version 0.3.15 of heroku toolbelt, heroku toolbelt will fail if an autoupdate is already in progress. Heroku toolbelt will check every 5 minutes for an update, so back-to-back heroku commands will fail unless another single heroku command has been run within the last 5 minutes. This behavior was introduced by this commit:
https://github.com/heroku/heroku/commit/023c84d15cde5958631b240eeaadec01a3b49031
I noticed this because it breaks heroku_san which typically makes multiple heroku commands back-to-back. Unfortunately, I don't see a workaround. It would help toolbelt could provide some sort of option to disable autoupdate or increase the time period for checks.
I'm having a hard time articulating my problem: when running the rails server within a file, the changes I made earlier today are not appearing on my local host. Yet, when I open the file in Sublime it shows that all of my code is there. It was working earlier today. I know it is not a rake database issue as the most recent changes I made to the model are showing up on the local host.
Link to github: https://github.com/BrianLobdell/depot
Please help!
-Brian
All I needed to do was run $ rake db:seed. still have no idea why I needed to run it again.
I cancelled a deployment to GAE while using django non-rel's manage.py deploy.
Now when I try to redeploy it says Another transaciton is already in progress and use appcfg to rollback.
But django non-rel doesn't have appcfg.py so how can I rollback or fix this issue?
I've scoured the internet and can't find any answers. I've waited about half an hour and it still displays this message.
manage.py deploy calls appcfg.py in order to deploy.
appcfg.py is in the SDK. you must have the SDK installed somewhere if "manage.py deploy" is working. you can look around for it, or download the SDK again.
There's no reason you don't have access to appcfg.py
If you need more help finding it, add details about what platform you're running on, where you installed the appengine SDK and where your python folder is.
What do you mean by "I don't have access to appcfg.py"?
Try going to cmd (for windows), navigate to your app directory, and type in the following:
appcfg.py rollback .
Hit return (enter key) and see if that works. If not, what does it display?