Trying to deploy to heroku, seems like the zlib module isn't playing nicely. Any ideas?
2012-08-16T20:50:07+00:00 heroku[slugc]: Slug compilation finished
2012-08-16T20:50:09+00:00 heroku[web.1]: Starting process with command `node web.js`
2012-08-16T20:50:09+00:00 app[web.1]:
2012-08-16T20:50:09+00:00 app[web.1]: node.js:134
2012-08-16T20:50:09+00:00 app[web.1]: throw e; // process.nextTick error, or 'error' event on first tick
2012-08-16T20:50:09+00:00 app[web.1]: ^
2012-08-16T20:50:09+00:00 app[web.1]: Error: Cannot find module 'zlib'
2012-08-16T20:50:09+00:00 app[web.1]: at Function._resolveFilename (module.js:320:11)
2012-08-16T20:50:09+00:00 app[web.1]: at Function._load (module.js:266:25)
2012-08-16T20:50:09+00:00 app[web.1]: at require (module.js:348:19)
2012-08-16T20:50:09+00:00 app[web.1]: at Object.<anonymous> (/app/node_modules/express/node_modules/connect/lib/middleware/compress.js:14:12)
2012-08-16T20:50:09+00:00 app[web.1]: at Module._compile (module.js:404:26)
2012-08-16T20:50:09+00:00 app[web.1]: at Object..js (module.js:410:10)
2012-08-16T20:50:09+00:00 app[web.1]: at Module.load (module.js:336:31)
2012-08-16T20:50:09+00:00 app[web.1]: at Function._load (module.js:297:12)
2012-08-16T20:50:09+00:00 app[web.1]: at require (module.js:348:19)
2012-08-16T20:50:09+00:00 app[web.1]: at Object.compress (/app/node_modules/express/node_modules/connect/lib/connect.js:89:14)
2012-08-16T20:50:11+00:00 heroku[web.1]: Process exited with status 1
2012-08-16T20:50:11+00:00 heroku[web.1]: State changed from starting to crashed
This was fixed in v1.4.11 of the Forge platform: http://docs.trigger.io/en/v1.4/release-notes.html#v1-4-11
Thanks for reporting!
turns out express got rid of its zlib dependency, so you have to add zlib (version "1.0") to package.json under /development/web
Update: this is fixed in v1.4.11
Related
I'm trying to deploy a Scala Play project on Heroku via Heroku CLI.
It works well, but when the server tries to start it crashes with the following error:
2021-08-17T16:47:52.333689+00:00 app[web.1]: at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:91)
2021-08-17T16:47:52.333713+00:00 app[web.1]: at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:306)
2021-08-17T16:47:52.333753+00:00 app[web.1]: at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
2021-08-17T16:47:52.333762+00:00 app[web.1]: at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:168)
2021-08-17T16:47:52.333789+00:00 app[web.1]: at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:39)
2021-08-17T16:47:52.333813+00:00 app[web.1]: at com.google.inject.internal.FactoryProxy.get(FactoryProxy.java:62)
2021-08-17T16:47:52.333838+00:00 app[web.1]: at com.google.inject.internal.InternalInjectorCreator.loadEagerSingletons(InternalInjectorCreator.java:213)
2021-08-17T16:47:52.333867+00:00 app[web.1]: at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:184)
2021-08-17T16:47:52.333893+00:00 app[web.1]: at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:111)
2021-08-17T16:47:52.333919+00:00 app[web.1]: at com.google.inject.Guice.createInjector(Guice.java:87)
2021-08-17T16:47:52.333942+00:00 app[web.1]: at com.google.inject.Guice.createInjector(Guice.java:78)
2021-08-17T16:47:52.333968+00:00 app[web.1]: at play.api.inject.guice.GuiceBuilder.injector(GuiceInjectorBuilder.scala:200)
2021-08-17T16:47:52.333993+00:00 app[web.1]: at play.api.inject.guice.GuiceApplicationBuilder.build(GuiceApplicationBuilder.scala:155)
2021-08-17T16:47:52.334018+00:00 app[web.1]: at play.api.inject.guice.GuiceApplicationLoader.load(GuiceApplicationLoader.scala:21)
2021-08-17T16:47:52.334042+00:00 app[web.1]: at play.core.server.ProdServerStart$.start(ProdServerStart.scala:53)
2021-08-17T16:47:52.334076+00:00 app[web.1]: at play.core.server.ProdServerStart$.main(ProdServerStart.scala:29)
2021-08-17T16:47:52.334102+00:00 app[web.1]: at play.core.server.ProdServerStart.main(ProdServerStart.scala)
2021-08-17T16:47:52.408221+00:00 heroku[web.1]: Process exited with status 255
2021-08-17T16:47:52.471552+00:00 heroku[web.1]: State changed from starting to crashed
2021-08-17T16:47:52.490499+00:00 heroku[web.1]: State changed from crashed to starting
2021-08-17T16:47:58.797308+00:00 heroku[web.1]: Starting process with command `target/universal/stage/bin/bionplaydatawarehouse -Dhttp.port=${PORT}`
2021-08-17T16:48:01.183756+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2021-08-17T16:48:01.398386+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -XX:+UseContainerSupport -Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8
2021-08-17T16:48:06.203049+00:00 app[web.1]: WARNING: An illegal reflective access operation has occurred
2021-08-17T16:48:06.203069+00:00 app[web.1]: WARNING: Illegal reflective access by com.google.inject.internal.cglib.core.$ReflectUtils$1 (file:/app/target/universal/stage/lib/com.google.inject.guice-4.2.3.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
2021-08-17T16:48:06.203069+00:00 app[web.1]: WARNING: Please consider reporting this to the maintainers of com.google.inject.internal.cglib.core.$ReflectUtils$1
2021-08-17T16:48:06.203070+00:00 app[web.1]: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
2021-08-17T16:48:06.203076+00:00 app[web.1]: WARNING: All illegal access operations will be denied in a future release
2021-08-17T16:48:15.071607+00:00 app[web.1]: Oops, cannot start the server.
The projet parameters are:
Play 2.8.8
Scala 2.13.5
SBT 1.5.0
Java 11
The project is based on an IntelliJ Ultimate Template.
The Heroku Procfile looks like this:
web: target/universal/stage/bin/bionplaydatawarehouse -Dhttp.port=${PORT}
The system.properties file looks like this to overwrite the default Java 8 Version:
java.runtime.version=11
When I change the Java Version the compilation crashes with a Class Cast Exception.
It seems that the Guice DI is the problem or some configuration parameter is missing for the Heroku production invironment because locally the projects works well.
I got it!
You need to add the -Dplay.http.secret.key argument which value must match your appliaction secret.
Unfortunately this was not part auf the documetation
web: target/universal/stage/bin/myProject -Dhttp.port=${PORT}
-Dplay.http.secret.key='mySecret'
2018-09-29T15:33:25.160299+00:00 heroku[web.1]: State changed from starting to crashed
2018-09-29T15:33:25.141050+00:00 heroku[web.1]: Process exited with status 1
Disconnected from log stream. There may be events happening that you do not see here! Attempting to reconnect...
2018-09-29T15:33:25.048441+00:00 app[web.1]: self.stop()
2018-09-29T15:33:25.048444+00:00 app[web.1]: File "/app/.heroku/python/lib/python3.6/site-packages/gunicorn/arbiter.py", line 393, in stop
2018-09-29T15:33:25.048656+00:00 app[web.1]: time.sleep(0.1)
2018-09-29T15:33:25.048693+00:00 app[web.1]: File "/app/.heroku/python/lib/python3.6/site-packages/gunicorn/arbiter.py", line 245, in handle_chld
2018-09-29T15:33:25.048898+00:00 app[web.1]: self.reap_workers()
2018-09-29T15:33:25.048910+00:00 app[web.1]: File "/app/.heroku/python/lib/python3.6/site-packages/gunicorn/arbiter.py", line 525, in reap_workers
2018-09-29T15:33:25.049163+00:00 app[web.1]: raise HaltServer(reason, self.WORKER_BOOT_ERROR)
2018-09-29T15:33:25.049169+00:00 app[web.1]: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3>`
Because of few details, we only knew it seems related to gunicorn.errors.HaltServer error.
You may refer to these and report what you found. Good luck!
It's a simple 2 page Sinatra app and Heroku returns the following error messages.
I tried placing config.ru and app.rb below app folder and root path
but both did not work...
Am I missing something?
2018-03-22T18:40:51.490531+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/bin/rackup:23:in `load'
2018-03-22T18:40:51.490533+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/bin/rackup:23:in `<top (required)>'
2018-03-22T18:40:53.657577+00:00 heroku[web.1]: Starting process with command `bundle exec rackup config.ru -p 22470`
2018-03-22T18:40:55.804338+00:00 heroku[web.1]: Process exited with status 1
2018-03-22T18:40:55.821099+00:00 heroku[web.1]: State changed from starting to crashed
2018-03-22T18:40:55.675952+00:00 app[web.1]: bundler: failed to load command: rackup (/app/vendor/bundle/ruby/2.4.0/bin/rackup)
2018-03-22T18:40:55.675970+00:00 app[web.1]: LoadError: cannot load such file -- ./app
2018-03-22T18:40:55.675972+00:00 app[web.1]: /app/config.ru:1:in `require'
2018-03-22T18:40:55.675973+00:00 app[web.1]: /app/config.ru:1:in `block in <main>'
2018-03-22T18:40:55.675974+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:55:in `instance_eval'
2018-03-22T18:40:55.675976+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:55:in `initialize'
2018-03-22T18:40:55.675977+00:00 app[web.1]: /app/config.ru:in `new'
2018-03-22T18:40:55.675978+00:00 app[web.1]: /app/config.ru:in `<main>'
2018-03-22T18:40:55.675980+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:49:in `eval'
2018-03-22T18:40:55.675981+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:49:in `new_from_string'
2018-03-22T18:40:55.675983+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:40:in `parse_file'
2018-03-22T18:40:55.675985+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:319:in `build_app_and_options_from_config'
2018-03-22T18:40:55.675986+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:219:in `app'
2018-03-22T18:40:55.675988+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:354:in `wrapped_app'
2018-03-22T18:40:55.675990+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:283:in `start'
2018-03-22T18:40:55.675991+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:148:in `start'
2018-03-22T18:40:55.675993+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/bin/rackup:4:in `<top (required)>'
2018-03-22T18:40:55.675995+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/bin/rackup:23:in `load'
2018-03-22T18:40:55.675997+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/bin/rackup:23:in `<top (required)>'
2018-03-22T18:44:05.000000+00:00 app[api]: Build succeeded
2018-03-22T18:44:40.562559+00:00 heroku[web.1]: State changed from crashed to starting
2018-03-22T18:44:42.586913+00:00 heroku[web.1]: Starting process with command `bundle exec rackup config.ru -p 5319`
2018-03-22T18:44:45.148047+00:00 heroku[web.1]: Process exited with status 1
2018-03-22T18:44:45.168235+00:00 heroku[web.1]: State changed from starting to crashed
2018-03-22T18:44:45.025605+00:00 app[web.1]: bundler: failed to load command: rackup (/app/vendor/bundle/ruby/2.4.0/bin/rackup)
2018-03-22T18:44:45.025629+00:00 app[web.1]: LoadError: cannot load such file -- sinatra/link_header
2018-03-22T18:44:45.025631+00:00 app[web.1]: /app/app/app.rb:2:in `require'
2018-03-22T18:44:45.025632+00:00 app[web.1]: /app/app/app.rb:2:in `<top (required)>'
2018-03-22T18:44:45.025634+00:00 app[web.1]: /app/config.ru:1:in `require'
2018-03-22T18:44:45.025635+00:00 app[web.1]: /app/config.ru:1:in `block in <main>'
2018-03-22T18:44:45.025637+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:55:in `instance_eval'
2018-03-22T18:44:45.025638+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:55:in `initialize'
2018-03-22T18:44:45.025641+00:00 app[web.1]: /app/config.ru:in `<main>'
2018-03-22T18:44:45.025640+00:00 app[web.1]: /app/config.ru:in `new'
2018-03-22T18:44:45.025642+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:49:in `eval'
2018-03-22T18:44:45.025644+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:49:in `new_from_string'
2018-03-22T18:44:45.025646+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:40:in `parse_file'
2018-03-22T18:44:45.025647+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:319:in `build_app_and_options_from_config'
2018-03-22T18:44:45.025649+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:219:in `app'
2018-03-22T18:44:45.025651+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:354:in `wrapped_app'
2018-03-22T18:44:45.025652+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:283:in `start'
2018-03-22T18:44:45.025654+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:148:in `start'
2018-03-22T18:44:45.025655+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/bin/rackup:4:in `<top (required)>'
2018-03-22T18:44:45.025657+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/bin/rackup:23:in `load'
2018-03-22T18:44:45.025659+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/bin/rackup:23:in `<top (required)>'
2018-03-22T19:04:36.398574+00:00 heroku[web.1]: Restarting
2018-03-22T19:04:36.399250+00:00 heroku[web.1]: State changed from up to starting
2018-03-22T19:04:37.265389+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2018-03-22T19:04:37.446567+00:00 heroku[web.1]: Process exited with status 1
2018-03-22T19:04:37.288342+00:00 app[web.1]: [4] - Gracefully shutting down workers...
2018-03-22T19:04:37.301303+00:00 app[web.1]: bundler: failed to load command: rackup (/app/vendor/bundle/ruby/2.4.0/bin/rackup)
2018-03-22T19:04:37.301330+00:00 app[web.1]: SignalException: SIGTERM
2018-03-22T19:04:37.301336+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/puma-3.11.3/lib/puma/cluster.rb:381:in `block in setup_signals'
2018-03-22T19:04:37.301338+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/puma-3.11.3/lib/puma/cluster.rb:475:in `select'
2018-03-22T19:04:37.301339+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/puma-3.11.3/lib/puma/cluster.rb:475:in `run'
2018-03-22T19:04:37.301340+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/puma-3.11.3/lib/puma/launcher.rb:183:in `run'
2018-03-22T19:04:37.301341+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/puma-3.11.3/lib/rack/handler/puma.rb:69:in `run'
2018-03-22T19:04:37.301343+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:297:in `start'
2018-03-22T19:04:37.301344+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/lib/rack/server.rb:148:in `start'
2018-03-22T19:04:37.301345+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/gems/rack-2.0.4/bin/rackup:4:in `<top (required)>'
2018-03-22T19:04:37.301347+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/bin/rackup:23:in `load'
2018-03-22T19:04:37.301392+00:00 app[web.1]: /app/vendor/bundle/ruby/2.4.0/bin/rackup:23:in `<top (required)>'
2018-03-22T19:04:38.773020+00:00 heroku[web.1]: Starting process with command `bundle exec rackup config.ru -p 16845`
2018-03-22T19:04:40.529326+00:00 heroku[web.1]: Process exited with status 1
2018-03-22T19:04:40.538335+00:00 heroku[web.1]: State changed from starting to crashed
2018-03-22T19:04:40.541186+00:00 heroku[web.1]: State changed from crashed to starting
2018-03-22T19:04:40.428727+00:00 app[web.1]: configuration /app/config.ru not found
2018-03-22T19:04:42.516252+00:00 heroku[web.1]: Starting process with command `bundle exec rackup config.ru -p 3071`
2018-03-22T19:04:44.810385+00:00 heroku[web.1]: Process exited with status 1
2018-03-22T19:04:44.823666+00:00 heroku[web.1]: State changed from starting to crashed
2018-03-22T19:04:44.653840+00:00 app[web.1]: configuration /app/config.ru not found
I just made the test, wrote a very simple Sinatra app and pushed it to Heroku.
Gemfile
source 'https://rubygems.org'
ruby '2.4.0'
gem 'sinatra'
config.ru
require './app'
run Sinatra::Application
app.rb
require 'sinatra'
get '/' do
"Hello world"
end
Launching rackup locally worked perfectly at this point, but when I pushed to heroku, I got an error as well, just like you. Looks like I was missing a Procfile. I then added a simple Procfile to tell Heroku what should be launched when running the app:
Procfile
web: bundle exec rackup config.ru -p $PORT
So at this point, I got this file hierarchy:
App directory
\
|– Gemfile
|– config.ru
|– app.rb
|– Procfile
And voilà, it now works perfectly. It might be worth giving it a shot and add this kind of Procfile to your project. You can find more details about Procfile on Heroku Getting started on Heroku with Ruby : Procfile and their devcenter article about process types and Procfiles.
After updating to Meteor 0.6.5 this https://github.com/jordansissel/heroku-buildpack-meteor doesn’t work any more. Logs from Heroku app:
2013-08-15T12:06:29+00:00 heroku[slug-compiler]: Slug compilation started
2013-08-15T12:06:43.647196+00:00 heroku[api]: Deploy 213bfc9 by artpolikarpov#getwear.com
2013-08-15T12:06:43.671450+00:00 heroku[api]: Release v350 created by artpolikarpov#getwear.com
2013-08-15T12:06:43.777150+00:00 heroku[web.1]: State changed from down to starting
2013-08-15T12:06:44+00:00 heroku[slug-compiler]: Slug compilation finished
2013-08-15T12:06:46.259053+00:00 heroku[web.1]: Starting process with command `PATH=.meteor/local/usr/bin:.meteor/local/usr/lib/meteor/bin:bin:/usr/local/bin:/usr/bin:/bin NODE_PATH=.meteor/local/usr/lib/meteor/lib/node_modules MONGO_URL=mongodb://heroku:c2130dda19da2b5a60ffae67ce4134a5#dharma.mongohq.com:10026/app14902610 .meteor/local/usr/lib/meteor/bin/node .meteor/local/build/main.js`
2013-08-15T12:06:46.926998+00:00 app[web.1]: module.js:340
2013-08-15T12:06:46.930406+00:00 app[web.1]: at Function.Module._resolveFilename (module.js:338:15)
2013-08-15T12:06:46.926865+00:00 app[web.1]:
2013-08-15T12:06:46.927270+00:00 app[web.1]: throw err;
2013-08-15T12:06:46.927270+00:00 app[web.1]: ^
2013-08-15T12:06:46.930406+00:00 app[web.1]: Error: Cannot find module '/app/.meteor/local/build/main.js'
2013-08-15T12:06:46.930406+00:00 app[web.1]: at Function.Module._load (module.js:280:25)
2013-08-15T12:06:46.930406+00:00 app[web.1]: at process.startup.processNextTick.process._tickCallback (node.js:244:9)
2013-08-15T12:06:46.930406+00:00 app[web.1]: at Module.runMain (module.js:492:10)
2013-08-15T12:06:48.127332+00:00 heroku[web.1]: Process exited with status 1
Can any one help?
Ok. Moving to another buildpack helped me. Now I’m using: https://github.com/oortcloud/heroku-buildpack-meteorite.
To move too, set new URL to the BUILDPACK_URL variable:
heroku config:set BUILDPACK_URL=https://github.com/oortcloud/heroku-buildpack-meteorite.git
To avoid the Meteor requires Node v0.8.24 or later error, define package.json in the root of your meteor project with the something like:
{
"name": "Whatever",
"version": "0.0.1",
"engines": {
"node": "0.8.24"
}
}
When deploying to heroku I get the following error log:
2013-08-05T18:14:39.217252+00:00 heroku[web.1]: State changed from crashed to starting
2013-08-05T18:14:43.819448+00:00 heroku[web.1]: Starting process with command `node server.js`
2013-08-05T18:14:45.272628+00:00 app[web.1]:
2013-08-05T18:14:45.274663+00:00 app[web.1]: module.js:340
2013-08-05T18:14:45.277076+00:00 app[web.1]: throw err;
2013-08-05T18:14:45.277256+00:00 app[web.1]: ^
2013-08-05T18:14:45.279157+00:00 app[web.1]: Error: Cannot find module '/app/server.js'
2013-08-05T18:14:45.279157+00:00 app[web.1]: at Function.Module._resolveFilename (module.js:338:15)
2013-08-05T18:14:45.279157+00:00 app[web.1]: at Function.Module._load (module.js:280:25)
2013-08-05T18:14:45.279157+00:00 app[web.1]: at Function.Module.runMain (module.js:497:10)
2013-08-05T18:14:45.279157+00:00 app[web.1]: at startup (node.js:119:16)
2013-08-05T18:14:45.279157+00:00 app[web.1]: at node.js:901:3
2013-08-05T18:14:46.719239+00:00 heroku[web.1]: Process exited with status 8
2013-08-05T18:14:46.736590+00:00 heroku[web.1]: State changed from starting to crashed
I'm new to derbyjs as well as heroku ... great, great, great tools, anyway!
So, why is the app complaining about a /app/server.js file?
It's a coffeescript project, and as far as I am aware, it uses browserify to deliver js on the fly. Also, there simply is no server.coffee in the app dir ... as it is the app dir, how can there ever be a server.js in it?? well, surely some meaning hidden from me for now.
Guys, can you help out?
I'm using:
Derby 0.5.9
Heroku Toolbelt ... just installed before writing this task
Deploy steps as explained on derbyjs.com
Cheers, Joehannes