I contacted the heroku support, my problem was fixed. 1, set your CNAME correctly(I used the namecheap domains) 2, after that, check that the heroku DNS target is the same as the namecheap host value. 3, restart the ACM (ssl) 4, you need to wait for several minutes to check the website.
The best idea we have found so far is to setup two Amazon EC2 micro machine instances with a small bit of nginx configuration. Then, provision two elastic IP addresses to point to those EC2 instances and point 2 A records to those IP addresses. This way, if something goes wrong on the hardware, you … Read more
The Cedar stack in Heroku does not appear to be responsive to the LOG_LEVEL config (env) variable that works for previous stacks (I use the logging:expanded addon). I tried setting LOG_LEVEL to both debug and DEBUG without success. Only by setting config.log_level = :debug in config/environments/production.rb am I able to see the output of ‘logger.debug’.
$ heroku config –app APP_NAME (The Heroku toolbelt has been updated since the question was asked; the command now shows the entire DATABASE_URL.)
We’re trying to be just that. Go to appharbor.com and sign up for an invite and we’ll be in touch soon more about AppHarbor: Real alternatives to Windows Azure PaaS (web role)?
Yes there are This is a very good post I found on the subject Heroku Alternatives : For Deploying Rails Applications I went over the options there one by one and, to my humble opinion, OpenShift is the best option for a small-medium website, at least for the beginning of developing and creating a POC\Prototype … Read more
You can dump a single table of data like so: $ pg_dump –no-acl –no-owner -h [host ip].compute-1.amazonaws.com -U [user name] -t [table name] –data-only [database name] > table.dump You can get all of the values needed with this: $ heroku pg:credentials:url [DATABASE] -a [app_name] Connection info string: “dbname=[database name] host=[host ip].compute-1.amazonaws.com port=5432 user=[user name] password=[password] … Read more
You can also setup a postintall command, something like this in your package.json “dependencies”: { “bower”: “0.6.x” }, “scripts”: { “postinstall”: “./node_modules/bower/bin/bower install” } Then npm install will also install bower dependencies. Pros : one command to rule them all. Cons : you unnecessarily embed bower as a dependency.