Re: Invitation not found - removing and changing Heroku Garden collaboration permissions
Same issue here. Has been a long standing (2-3 months) problem that collaborators can't be deleted. Waldo On May 9, 11:39 pm, ptorrsmith ptorrsm...@gmail.com wrote: Hiya from way down under :-) Can't appear to delete or upgrade collaborator invites to Heroku Garden. When I click on the x to delete a collaborator, I get a blank page with Invitation not found. I tried to upgrade a collaborator from view to edit by reinviting them with edit rights, but no success. Get page refreshed with flash message of # :-) Any suggestions? Thanks Peter --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
how to run rails app in production mode on heroku.com ?
I have a simple application with the Post table (generated with scaffold command scaffold post title:string) (sqlite3, utf-8 encoding in db) with 1 column is title, Further on the local computer, I do, rake db: migrate RAILS_ENV = production and ruby script/server -e production, in the browser entered localhost: 3000/posts and I turn to the presentation and I can add entries in the production table. at heroku, I tried the following ways: heroku config: add RAILS_ENV=production rake db: migrate RAILS_ENV=production and when I turn on http://myappname.heroku.com/posts and see the error Error 503 Service Unavailable,: ( I also add a line ENV[ 'RAILS_ENV'] | | = 'production' in the file environment.rb, but it also does not work, run in development. I have one idea to simply replace the contents of the file containing the file development.rb production.rb, but it is not nice = / Dear friends, help me. (sorry for my bad english) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Mephisto and read only file system
Hi,
I read Adam's entry that he had got Mephisto running on heroku...
However I get read only file system errors.
Is there any work around?
Here's the stack trace:
Processing MephistoController#dispatch (for 203.97.nnn.nnn at
2009-05-10 03:35:29) [GET]
Parameters: {action=dispatch, controller=mephisto, path=
[]}
Errno::EROFS (Read-only file system - /disk1/home/slugs/
14579_c8bad6a_f265/mnt/themes/site-1 - Heroku has a read-only
filesystem. See http://heroku.com/docs#toc59):
/usr/local/lib/ruby/1.8/fileutils.rb:243:in `mkdir'
/usr/local/lib/ruby/1.8/fileutils.rb:243:in `fu_mkdir'
/usr/local/lib/ruby/1.8/fileutils.rb:217:in `mkdir_p'
/usr/local/lib/ruby/1.8/fileutils.rb:215:in `reverse_each'
/usr/local/lib/ruby/1.8/fileutils.rb:215:in `mkdir_p'
/usr/local/lib/ruby/1.8/fileutils.rb:201:in `each'
/usr/local/lib/ruby/1.8/fileutils.rb:201:in `mkdir_p'
/app/models/site.rb:147:in `themes'
/app/models/site.rb:159:in `theme'
(__DELEGATION__):2:in `templates'
/app/models/site.rb:244:in `find_preferred_template'
/app/models/site.rb:304:in `set_content_template'
/app/models/site.rb:201:in `call_render'
/app/controllers/application.rb:87:in `render_liquid_template_for'
/app/controllers/mephisto_controller.rb:29:in `dispatch_list'
/app/controllers/mephisto_controller.rb:11:in `send'
/app/controllers/mephisto_controller.rb:11:in `dispatch'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/base.rb:1253:in `send'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/base.rb:1253:in `perform_action_without_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:617:in `call_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:638:in `run_before_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:206:in `call'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:206:in `around_proc'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.2.2/lib/
active_support/callbacks.rb:182:in `call'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.2.2/lib/
active_support/callbacks.rb:182:in `evaluate_method'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:184:in `call'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:635:in `run_before_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:615:in `call_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:638:in `run_before_filters'
/app/controllers/application.rb:108:in `get_requests_are_readonly'
/config/initializers/readonly_records.rb:18:in
`with_readonly_records'
/app/controllers/application.rb:107:in `get_requests_are_readonly'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.2.2/lib/
active_support/callbacks.rb:178:in `send'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.2.2/lib/
active_support/callbacks.rb:178:in `evaluate_method'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:186:in `call'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:635:in `run_before_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:615:in `call_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:610:in `perform_action_without_benchmark'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/benchmarking.rb:68:in
`perform_action_without_rescue'
/usr/local/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/benchmarking.rb:68:in
`perform_action_without_rescue'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/rescue.rb:136:in `perform_action_without_caching'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/caching/sql_cache.rb:13:in `perform_action'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.2.2/lib/
active_record/connection_adapters/abstract/query_cache.rb:34:in
`cache'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.2.2/lib/
active_record/query_cache.rb:8:in `cache'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/caching/sql_cache.rb:12:in `perform_action'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/base.rb:524:in `send'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/base.rb:524:in `process_without_filters'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/
action_controller/filters.rb:606:in
`process_without_session_management_support'
Re: Handle incoming e-mails
You could further automate that process with the upcomming workling support. Best regards, DBA On May 9, 12:33 am, Morten Bagai mor...@heroku.com wrote: I think I'd just set up Google apps to handle email for my domain, and use one the available POP3 or IMAP libs to check whatever account I want my Ruby app to process. /Morten On May 7, 2009, at 1:37 AM, Thomas Balthazar wrote: Hello, I've seen a lot of posts about handling outgoing e-mails. But what would be the best solution to handle incoming e-mails? Having a server elsewhere (Slicehost, Mosso, ...), configured with Postfix and a Rails app that handle/parse incoming e-mails, then ping the Heroku app with the data? Thanks for sharing your ideas. Best, Thomas. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Git Submodule Support
It's definitely a pain not having this support. I'm developing a component, with a master repo at github, which is a plugin for my rails app. It's painful having to mess around every time I bring a new component change into the app. GaJ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
