Note that there are some explanatory texts on larger screens.

plurals
  1. POCompoundJS error when deploying to Heroku or Nodejitsu
    primarykey
    data
    text
    <p>I'm trying to deploy a compoundjs (a.k.a. railwayjs) to Heroku or Nodejitsu as a my first end to end test of NodeJS. </p> <p>Steps</p> <ol> <li>Node installation: 0.8.16</li> <li>Heroku tools installation</li> <li>npm install compound -g (v1.1.4-1)</li> <li><p>Sample heroku app as described in <a href="http://compoundjs.com/docs/#heroku-heroku" rel="nofollow">CompoundJS's Heroku guide</a></p> <pre><code>compound init heroku-app cd heroku-app sudo npm link compound g crud post title content </code></pre></li> <li><p>Adjustment in packages.json: added engines as follows</p> <pre><code>"engines": { "node": "0.8.x", "npm": "1.1.x" }, </code></pre></li> <li><p>foreman start -> application works perfect</p></li> <li>git add and commit</li> <li>git push heroku master</li> <li>heroku ps:scale web=1 (only first time)</li> </ol> <p>After that, application is deployed and accesible through a test host of heroku. Application index works ok, but an <a href="http://pastebin.com/H1WEdd9c" rel="nofollow">error page</a> is displayed when trying to create a new blog post. </p> <p>According other reports, this issue is related with dependencies versions. According to git push output to heroku, following versions are being used:</p> <pre><code> Resolving engine versions Using Node.js version: 0.8.14 Using npm version: 1.1.65 .... (main dependencies) npm http GET https://registry.npmjs.org/ejs/-/ejs-0.8.3.tgz npm http GET https://registry.npmjs.org/coffee-script/-/coffee-script-1.4.0.tgz npm http 200 https://registry.npmjs.org/seedjs npm http GET https://registry.npmjs.org/seedjs/-/seedjs-0.0.4.tgz npm http 200 https://registry.npmjs.org/compound npm http 200 https://registry.npmjs.org/ejs-ext/-/ejs-ext-0.1.4.tgz npm http 200 https://registry.npmjs.org/express npm http GET https://registry.npmjs.org/compound/-/compound-1.1.4-1.tgz npm http GET https://registry.npmjs.org/express/-/express-3.0.5.tgz npm http 200 https://registry.npmjs.org/jugglingdb npm http 200 https://registry.npmjs.org/stylus npm http 200 https://registry.npmjs.org/ejs/-/ejs-0.8.3.tgz npm http GET https://registry.npmjs.org/jugglingdb/-/jugglingdb-0.2.0-9.tgz npm http GET https://registry.npmjs.org/stylus/-/stylus-0.31.0.tgz npm http 200 https://registry.npmjs.org/coffee-script/-/coffee-script-1.4.0.tgz npm http 200 https://registry.npmjs.org/seedjs/-/seedjs-0.0.4.tgz npm http 200 https://registry.npmjs.org/stylus/-/stylus-0.31.0.tgz npm http 200 https://registry.npmjs.org/express/-/express-3.0.5.tgz npm http 200 https://registry.npmjs.org/compound/-/compound-1.1.4-1.tgz </code></pre> <p>I face the same issue when deploying to nodejitsu (exactly the same). Any idea ? I'm poiting to specific dependencies versions, so I assume that this is issue would not be related with outdated dependencies used in server.</p> <p>Thanks.</p> <p>UPDATE with Nodejitsu related information: </p> <p>Nodejitsu log on jitsu deploy</p> <pre><code> info: Welcome to Nodejitsu storni info: jitsu v0.11.4, node v0.8.16 info: It worked if it ends with Nodejitsu ok info: Executing command deploy info: Analyzing application dependencies in server.js warn: Local package version appears to be old warn: The package.json version will be incremented automatically warn: About to write F:\repo\mine\last-jitsu-test\package.json data: data: { data: scripts: { test: 'nodeunit test/*/*', start: 'server.js' }, data: name: 'last-jitsu-test', data: version: '0.0.1-5', data: dependencies: { data: coffee-script: '&gt;= 1.1.1', data: stylus: '0.31.0', data: seedjs: '0.0.4', data: compound: '1.1.4-1', data: ejs-ext: '0.1.4', data: express: '3.0.5', data: ejs: '0.8.3', data: jugglingdb: '&gt;= 0.1.0' data: }, data: devDependencies: { data: sinon: '*', data: semicov: '*', data: nodeunit: '*' data: }, data: subdomain: 'storni.last-jitsu-test', data: main: 'server.js', data: engines: { npm: '1.1.x', node: '0.8.x' } data: } data: prompt: Is this ok?: (yes) info: Creating snapshot 0.0.1-5 info Uploading: [=============================] 100% info: Updating app last-jitsu-test info: Activating snapshot 0.0.1-5 for last-jitsu-test info: Starting app last-jitsu-test info: App last-jitsu-test is now started info: http://storni.last-jitsu-test.jit.su on Port 80 info: Nodejitsu ok </code></pre> <p>storni.last-jitsu-test.jit.su/items -> Works ok storni.last-jitsu-test.jit.su/items/new -> Displays the same error page as in Heroku deployment.</p> <p>In this scenario, I've tested locally with vanilla </p> <pre><code> node server.js </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload