I am using Compass with several apps on Heroku. Compass compiles the
stylesheets (.css) to public/stylesheets/compiled for me and what I
have done is to check those compiled CSS output files into my Git repo
that gets pushed to Heroku.
I did not have to specifically modify the config at all to work on
Heroku. I initially setup and configured compass using the scripts
provided here:
http://wiki.github.com/chriseppstein/compass/ruby-on-rails-integration
HTH
G
On Feb 17, 9:34 am, sslguy wrote:
> Thanks for the response. So I'm thinking I should disable compass. Has
> anyone gotten compass to work on Heroku?
>
> On Feb 16, 9:13 pm, bdeank wrote:
>
>
>
> > Looks like compass is trying to recompile your stylesheets, and can't
> > because Heroku FS is read-only.
>
> > On Feb 16, 8:54 pm, sslguy wrote:
>
> > > Here is what I was able to pull from the logs immediately following a
> > > 500 error:
>
> > > ==> dyno-878231.log <==
> > > config.gem: Unpacked gem environment.rb in vendor/gems has no
> > > specification file. Run 'rake gems:refresh_specs' to fix this.
> > > config.gem: Unpacked gem environment.rb in vendor/gems not in a
> > > versioned directory. Giving up.
> > > config.gem: Unpacked gem ruby in vendor/gems has no specification
> > > file. Run 'rake gems:refresh_specs' to fix this.
> > > config.gem: Unpacked gem ruby in vendor/gems not in a versioned
> > > directory. Giving up.
>
> > > ==> production.log <==
> > > # Logfile created on Tue Feb 16 17:50:59 -0800 2010
>
> > > Processing ApplicationController#new (for 98.201.58.81 at 2010-02-16
> > > 17:51:00) [GET]
>
> > > Errno::EROFS (Read-only file system - /disk1/home/slugs/
> > > 129005_3d87b71_003c/mnt/public/stylesheets/compiled/ie.css - Heroku
> > > has a read-only filesystem.
> > > Seehttp://docs.heroku.com/constraints#read-only-filesystem):
> > > haml (2.2.3) rails/./lib/sass/plugin.rb:79:in `delete'
> > > haml (2.2.3) rails/./lib/sass/plugin.rb:79:in `update_stylesheet'
> > > haml (2.2.3) rails/./lib/sass/plugin.rb:69:in `update_stylesheets'
> > > haml (2.2.3) rails/./lib/sass/plugin.rb:64:in `each'
> > > haml (2.2.3) rails/./lib/sass/plugin.rb:64:in `update_stylesheets'
> > > haml (2.2.3) rails/./lib/sass/plugin.rb:62:in `each'
> > > haml (2.2.3) rails/./lib/sass/plugin.rb:62:in `update_stylesheets'
> > > haml (2.2.3) rails/./lib/sass/plugin/rails.rb:16:in
> > > `process_without_compass'
> > > /home/slugs/129005_3d87b71_003c/mnt/.gems/gems/chriseppstein-
> > > compass-0.8.17/lib/compass/app_integration/rails/action_controller.rb:
> > > 7:in `process'
> > > /home/heroku_rack/lib/static_assets.rb:9:in `call'
> > > /home/heroku_rack/lib/last_access.rb:25:in `call'
> > > /home/heroku_rack/lib/date_header.rb:14:in `call'
> > > thin (1.0.1) lib/thin/connection.rb:80:in `pre_process'
> > > thin (1.0.1) lib/thin/connection.rb:78:in `catch'
> > > thin (1.0.1) lib/thin/connection.rb:78:in `pre_process'
> > > thin (1.0.1) lib/thin/connection.rb:57:in `process'
> > > thin (1.0.1) lib/thin/connection.rb:42:in `receive_data'
> > > eventmachine (0.12.6) lib/eventmachine.rb:240:in `run_machine'
> > > eventmachine (0.12.6) lib/eventmachine.rb:240:in `run'
> > > thin (1.0.1) lib/thin/backends/base.rb:57:in `start'
> > > thin (1.0.1) lib/thin/server.rb:150:in `start'
> > > thin (1.0.1) lib/thin/controllers/controller.rb:80:in `start'
> > > thin (1.0.1) lib/thin/runner.rb:173:in `send'
> > > thin (1.0.1) lib/thin/runner.rb:173:in `run_command'
> > > thin (1.0.1) lib/thin/runner.rb:139:in `run!'
> > > thin (1.0.1) bin/thin:6
> > > /usr/local/bin/thin:20:in `load'
> > > /usr/local/bin/thin:20
>
> > > Rendering /disk1/home/slugs/129005_3d87b71_003c/mnt/public/500.html
> > > (500 Internal Server Error)
>
> > > Any ideas?
>
> > > On Feb 16, 12:42 am, Pedro Belo wrote:
>
> > > > Do you see anything by running heroku logs?
> > > > 500s are caused by the application, so you should find the source of
> > > > it in the logs.
>
> > > > On Mon, Feb 15, 2010 at 9:32 PM, sslguy wrote:
> > > > > Looks like the problem still exists :(
>
> > > > > On Feb 15, 4:42 pm, sslguy wrote:
> > > > >> Thanks for your prompt response. I'll check back in a while to see if
> > > > >> the 500 error resurfaces.
>
> > > > >> On Feb 15, 11:14 am, Oren Teich wrote:
>
> > > > >> > While free apps do cycle down after a few hours of inactivity, you
> > > > >> > should
> > > > >> > never get a 500 error. That's something we'll have to look into.
>
> > > > >> > Oren
>
> > > > >> > 2010/2/15 Nicolás Sanguinetti
>
> > > > >> > > On Mon, Feb 15, 2010 at 2:15 PM, sslguy
> > > > >> > > wrote:
> > > > >> > > > Any idea why my app ssltools.com keeps winding down. When I
> > > > >> > > > visit the
> > > > >> > > > site, I at first get an error code 500. Upon immediate
> > > > >> > > > refresh, the
> > > > >> > > > app comes up. However, wait a period of time, and Heroku shuts
> > > > >> > > > the app
> > > > >> > > > down. Then the c
