MySQL’s totally non standards compliant GROUP BY can be emulated by Postgres’ DISTINCT ON. Consider this: MySQL: SELECT a,b,c,d,e FROM table GROUP BY a This delivers 1 row per value of a (which one, you don’t really know). Well actually you can guess, because MySQL doesn’t know about hash aggregates, so it will probably use … Read more
As Heroku’s dynos don’t have a filesystem that persists across deploys, a file-based database like SQLite3 isn’t going to be suitable. It’s a great DB for development/quick prototypes, though. Heroku do have a Postgres offering however that will suit – with a free tier and a basic $9/month tier that are good for hobby/small projects. … Read more
If you have npm version 5 or above, try this first: $ sudo npm cache verify Otherwise: $ sudo npm cache clean My node and npm versions are: $ node -v v0.10.0 $ npm -v 1.2.14 https://docs.npmjs.com/cli/cache
Second Update The FAQ is not available anymore. From the documentation of shrinkwrap: If you wish to lock down the specific bytes included in a package, for example to have 100% confidence in being able to reproduce a deployment or build, then you ought to check your dependencies into source control, or pursue some other … Read more
File-based databases aren’t a good fit for Heroku due to its ephemeral filesystem (bold added): Each dyno gets its own ephemeral filesystem, with a fresh copy of the most recently deployed code. During the dyno’s lifetime its running processes can use the filesystem as a temporary scratchpad, but no files that are written are visible … Read more
Heroku doesn’t support SQLite databases. You need to use PostgreSQL on production, as I also explained in this post. group :production do gem “pg” end group :development, :test do gem “sqlite3”, “~> 1.3.0” end Actually, it’s recommended to use in development/test an environment as close as possible to production. Therefore, I suggest you to switch … Read more
I have no idea what Yesod is, but I know exactly what each of your other errors means. First, you should not try to link statically. The warning you get is exactly right: if you link statically, and use one of the routines for which you are getting the warning, then you must arrange to … Read more
Heroku dynamically assigns your app a port, so you can’t set the port to a fixed number. Heroku adds the port to the env, so you can pull it from there. Switch your listen to this: .listen(process.env.PORT || 5000) That way it’ll still listen to port 5000 when you test locally, but it will also … Read more
TL;DR: Until this is resolved, see instructions for migrating from GitHub deployment to Git deployment below. It is unlikely to be resolved any time soon: We take the protection of our customers very seriously, and as a result, we will not be reconnecting to GitHub until we are certain that we can do so safely, … Read more