Heroku dynos have an ephemeral filesystem (https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem). Since you are using SQLite which is actually a file on the filesystem, everything will run smoothly until the dyno running your application needs to restart – so its filesystem will be reset and you’ll lose everything ! To avoid it just configure your application to use Heroku-Postgresql.
You’re using mongoose 3.8.19. The latest version of mongoose is 4.1.9. I would start there: $ npm install –save –save-exact [email protected]
Go on Heroku, on your application, go to settings, hit Reveal Config Vars. Click on on Edit on the right side and enter your secrets there: S3_BUCKET: name of your bucket goes here S3_ACCESS_KEY: xxxxx S3_SECRET_KEY: xxxx On config/initializers/carrierwave.rb or wherever you’re entering your secrets should have: CarrierWave.configure do |config| config.root = Rails.root.join(‘tmp’) # adding … Read more
EDITED: As @mipadi has pointed out here (http://stackoverflow.com/questions/13001031/django-heroku-settings-injection/13092534), it can actually be as simple as this: import dj_database_url DATABASES = {‘default’ : dj_database_url.config() } This works if you have a DATABASE_URL env variable set. heroku:pg_promote gets your there. Details below Make sure you have Postgres on your Heroku heroku addons:add heroku-postgresql:dev Step 1: figure out … Read more
The problem is that the mysql2 gem is not installing with its native dependencies. In previous versions of Ruby, this would have triggered the unable to build native gem extension error: Something has changed in Ruby 2.2 so that you can install the gem without it building the native extension. This does not mean the … Read more
I fixed mine by opening Gemfile.lock and deleting the following two lines: PLATFORMS x86-mingw32 So now i just need to make a script that bundles then removes that from the lock file.
I don’t see it in your code above, but guessing you probably have your gem ‘sqlite3’ at the top of your gemfile, so it is being used in all environments. Sqlite is not supported on Heroku so it has be kept out of the production group. Try the following so that you can use sqlite … Read more
This is most likely the result of scaling your web processes down to zero through the client. $ heroku ps:scale web=0 Use the heroku ps command to determine the state of your web processes., and you should take a look at the Error Codes to understand the Heroku functionality.
I had a similar problem. I just ssh into heroku dyno with: heroku run bash ( from your heroku application folder ofc ) Than run all the migration and makemigration commands with createsuperuser if needed. Works with sqlite and postgre for me.
Eventually solved this using the below in my urls file – from this question: Heroku – Handling static files in Django app from <app> import settings urlpatterns += patterns(”, (r’^static/(?P<path>.*)$’, ‘django.views.static.serve’, {‘document_root’: settings.STATIC_ROOT}), )