Here is what worked for me when I deployed to Heroku. http://flask-cors.readthedocs.org/en/latest/ Install flask-cors by running – pip install -U flask-cors from flask import Flask from flask_cors import CORS, cross_origin app = Flask(__name__) cors = CORS(app) app.config[‘CORS_HEADERS’] = ‘Content-Type’ @app.route(“https://stackoverflow.com/”) @cross_origin() def helloWorld(): return “Hello, cross-origin-world!”
In case you’re using virtualenvwrapper (I highly recommend doing so), you can define different hooks (preactivate, postactivate, predeactivate, postdeactivate) using the scripts with the same names in $VIRTUAL_ENV/bin/. You need the postactivate hook. $ workon myvenv $ cat $VIRTUAL_ENV/bin/postactivate #!/bin/bash # This hook is run after this virtualenv is activated. export DJANGO_DEBUG=True export S3_KEY=mykey export … Read more
Had the same issue, as its a shared space on AWS with 1000 other DBs. pgAdmin 3 Make sure you are disconnected from your server. Right click your Server -> properties -> Advanced tab. In ‘DB restriction’ type in the name of your database(s) enclosed in single quotes and separated by spaces. E.g. ‘dback447’ pgAdmin … Read more
You can push an alternative branch to Heroku using Git. git push heroku-dev test:master This pushes your local test branch to the remote’s master branch (on Heroku). Comment from @Brian Armstrong: Worth noting also, when you’re ready to go back to master you need to do git push -f heroku master:master
Do git status, this will show you what files have changed. Since you stated that you don’t want to keep the changes you can do git checkout — <file name> or git reset –hard to get rid of the changes. For the most part, git will tell you what to do about changes. For example, … Read more
Open the “Properties” of the Heroku server in pgAdminIII and change the “Maintenance DB” value to be the name of the database you want to connect to. The default setup is suitable for DBAs et al who can connect to any database on the server, but apparently that isn’t true in your case.
Sprockets together with Sass has some nifty helpers you can use to get the job done. Sprockets will only process these helpers if your stylesheet file extensions are either .css.scss or .css.sass. Image specific helper: background-image: image-url(“logo.png”) Agnostic helper: background-image: asset-url(“logo.png”, image) background-image: asset-url($asset, $asset-type) Or if you want to embed the image data in … Read more
The answer was: heroku restart -a app_name # The -a is the same as –app Easily aliased with alias hra=”heroku restart –app ” Which you can make a permanent alias by adding it to your .bashrc or .bash_aliases file as described at: https://askubuntu.com/questions/17536/how-do-i-create-a-permanent-bash-alias and Creating permanent executable aliases Then you can just type hra app_name … Read more
To completely ‘stop’ your app you can scale the web dynos down to zero which effectively takes all your app http-processes offline. $ heroku ps:scale web=0 Scaling web processes… done, now running 0
As of May 25, 2022, at 19:52 UTC, GitHub integration has been re-enabled: We are happy to report that the GitHub integration is re-enabled! You can now reconnect with GitHub and restore your Heroku pipeline functionality, including Review Apps, with newly generated tokens. You can connect to GitHub immediately or wait for the enhanced integration … Read more