Re: Connecting to EC2 services Security
On Wed, Apr 4, 2012 at 6:13 PM, Eric Jain eric.j...@gmail.com wrote: If I follow the instructions at https://devcenter.heroku.com/articles/external-services, any Heroku app will be able to connect to my security group. Correct? Correct. Adam -- 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: Same-dyno communication via TCP sockets (for worker task)
How about a FIFO? Use mkfifo to create a named pipe inside your ephemeral filesystem, then launch your two child processes. One can write to it, the other can read. So using your bash example: $ heroku run bash ~ $ mkfifo myfifo ~ $ cat myfifo | ./run_listener_process ~ $ ./run_other_process_that_sends_data myfifo Adam -- 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: basic question about dyno RAM
On Fri, Nov 25, 2011 at 11:16 AM, anentropic bluesk...@gmail.com wrote: Is this broadly comparable to Heroku... i.e. the whole 512MB is available to user processes? Yes, all 512MB goes to your processes. Adam -- 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: Multiple Apps, Multiple Clients. One Account?
On Fri, Nov 25, 2011 at 12:55 PM, anentropic bluesk...@gmail.com wrote: I found a place in the FAQs where it says Each application receives 750 free dyno hours per month but would like to confirm that it really is per app. Correct, it's per-app. Adam -- 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: fatal: Not a git repository (or any of the parent directories): .git
Slugs don't have git repositories in them. Something in your app is trying to do a Git operation when it boots -- you should figure out what it is and remove it. You can duplicate it locally by moving your .git directory to .git-bak, and then try running your app. Adam -- 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: Cannot acces app in Console
What do you run locally to get a console? Whatever it is, prefix it with `heroku run` and you should be set. e.g. if you normally type: $ bundle exec rails console Then to run remotely: $ heroku run 'bundle exec rails console' Or if it's a Sinatra app: $ bundle exec irb -r ./web On Heroku: $ heroku run 'bundle exec irb -r ./web' Adam -- 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: Procfile, cedar and logs
You might try putting this at the top of your email:work task: STDOUT.sync = true Ruby buffers output by default, which can cause it to delay appearing in the logs until you have enough output. Adam -- 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: Caching POST Requests
On Tue, Oct 11, 2011 at 7:32 PM, Karl threadh...@gmail.com wrote: 2011-10-11T20:53:27+00:00 app[web.1]: cache: [POST /printed.xml] invalidate, pass What does the cache: [...] invalidate, pass mean? Note that the log originates with your app, process name web.1. This is coming from your app, not Heroku infrastructure. It's a Rails log message. Adam -- 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: Cedar migrations
On Mon, Jul 11, 2011 at 9:51 AM, Neil Middleton neil.middle...@gmail.comwrote: ruby-1.9.2 ~/code/rest_test (master) ➔ heroku run rake db:migrate Unknown command. Run 'heroku help' for usage information. You probably need to update to the latest Heroku gem: `gem install heroku` Adam -- 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: [Help!] DelayedJob workers die with no warnign or SIGTERM
Cristiano - Is your app in maintenance mode? Adam -- 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: H12 errors, blocked dynos and Heroku website claims.
On Thu, Feb 17, 2011 at 7:15 AM, Michael Abner mike.ab...@gmail.com wrote: In this situation I would think you'd want to upload to s3 directly and the fire off a background worker to go and do the resizing for you. That would keep your web dynos available to serve your requests. Exactly right. Uploads straight to S3 from the browser are fantastic, you should use them if you're doing any kind of substantial upload processing. Moral of the story: never, ever block the web process for long ( 1 second) periods of time - there's always a better way. Follow this practice and you and your users will always be happy campers. I certainly extend my apologies to you, Christos, and anyone else inconvenienced by the incorrect docs. I've tweaked the performance concepts doc to remove some of the more glaring inaccuracies, which will hopefully tide us over until we can rewrite the whole thing to cover the broader array of concurrency models we can handle. Adam -- 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: Help getting app to start running?
On Sun, Jan 30, 2011 at 5:06 PM, Jason Preston jasonp...@gmail.com wrote: as part of my user model (built from scrach) I explicitly called require 'Digest' in order to do a one-way hash on user passwords, I'm guessing that was the issue. The problem here might be that your local filesystem is case-insensitive (e.g., if you're on OS X) but the filesystem on Heroku is case-sensitive (since it's Linux). Therefore you want to make sure to use the correct case for the ruby file you're loading, which is probably: require 'digest' Adam -- 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: Is there a way to be notified on Backlog Too Deep or Request Timeout?
We've got some features in mind that should provide a good solution for this use-case. In the meantime, the best workaround I can suggest if you really need this would be to install the advanced logging add-on, direct the logs to your own syslog instance, and set up some kind of log analysis script there that emails you when it spots the string Error H11. Adam -- 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: tailing heroku logs does not work
Make sure you have the latest Heroku gem: $ gem install heroku Adam -- 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: Why is this Eventmachine process being terminated?
On Wed, Dec 15, 2010 at 1:46 PM, Jonas jo...@jonasbnielsen.dk wrote:
For people playing around with the daemons gem, this is the equivalent
of setting the :ontop option to true. (http://daemons.rubyforge.org/
classes/Daemons.html#M04)
I suggest not using the Daemons gem at all. Here's a hello-world
eventmachine daemon running via the DJ convention in your Rakefile:
task 'jobs:work' do
require 'eventmachine'
EM.run do
EM.add_periodic_timer(1) do
puts Tick! #{Time.now}
end
end
end
Dustin Sallings, one of the authors of memcached, put it beautifully
when he said: Self-daemonizing programs start you down the path to
hell.. See:
http://dustin.github.com/2010/02/28/running-processes.html
Adam
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@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: Request timeouts
Thanks for the thoughtful description of your situation, Josal. We appreciate your trust and are working very hard to continue to deserve it! Regarding unexpected timeouts, what we've seen is that they are almost always a result of what I call a wedged process. I blogged about this a couple years ago: http://adam.heroku.com/past/2008/6/17/battling_wedged_mongrels_with_a/ What happens is that one request does something that locks the process (like hitting a remote API that never returns, or calling a method with an infinite loop bug). Once this occurs, the process can't serve any future requests, and all requests sent to it will time out - even simple requests for non-dynamic pages or static assets not already in the Varnish cache. The only solution to the wedged process problem is to restart the process. This is not a problem unique to Heroku in any way; however, running on Heroku gives you fewer options for live introspection of the processes' behavior. For example, if you hit this problem on Slicehost you might install the mongrel_proctitle plugin in order to find out which request the process is stuck on. We're working on expanding the number of options you have for diagnosing these situations. In the meantime, your best options are: - Use heroku restart to reboot your processes when you suspect one is wedged. - Use the SystemTimeout method described in the blog post above, with a timeout of 29 seconds or less. Unfortunately this still doesn't catch every kind of wedging (certain kinds of system calls won't be trapped by it), but it can catch many of them. - Use our new logging system, currently in private beta, for more detailed introspection of requests. I'll email you privately with the details. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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.
[ANN] new crashed process handling
We've just rolled out a new version of our process manager, with streamlined handling of crashed processes. A lot of you guys have been frustrated when your workers crash (libXML segfaults, for example) because the restart behavior was somewhat unpredictable. The new version follows a very simple algorithm: any process that crashes will be restarted immediately, with a cooldown time of ten minutes. This applies to all process types including web processes (dynos). We've also unified the behavior of crashed dynos with crashed workers. Now if you push up a bad deploy (missing a gem, etc) you won't be shown the stack trace in the browser, and instead can find the stack trace and debugging info by running heroku logs. This makes the workflow for handling a crashed process the same as handling an exception during the request cycle (HTTP 500): your users are displayed a generic page, and you the developer can look up the problem in your logs. A description of the new crash policy, and some documentation for the heroku ps command (great for introspecting on the state of your processes) can be found here: http://docs.heroku.com/ps We welcome your feedback. Please reply (here on the mailing list, or to me privately) if you have any thoughts, especially if you've seen it in action on your own crashed processes. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Using Rack::StaticCache
Great discussion in this thread. Matthew, your analysis and monkey-patch are very impressive! I'm just sorry you guys are stuck reverse-engineering this portion of our stack to get your apps working the way you want - that's definitely bad on us. We're hoping to be able to make heroku_rack open source soon, which should make it a lot easier to get in and tinker with stuff like this. In the meantime, here's the static asset middleware: http://gist.github.com/480819 One solution here might be to extend can_cache? so that it checks to make sure there isn't already a cache header and thereby avoid clobbering it in the case of a user setting the value. I can't imagine why changing pathnames would affect caching behavior, though. We don't do anything special with paths. Nor has anything in this component changed recently, the last commit on the static asset middleware was in late 2009. -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: A conclusive way to package static assets
On Sat, Jul 17, 2010 at 10:57 PM, Ben Schwarz ben.schw...@gmail.com wrote: Can you explain how dynos work across file systems? Can `/tmp` be relied upon with multiple dynos? (disregarding the fact that `/tmp` will be cleared at random intervals.) Your dynos are running on different machines, with no filesystem shared between them. I wouldn't recommend write to /tmp, since it's world-readable as per unix convention. Instead, use the tmp dir under your app's root, which is a scratchpad only your dyno can access. e.g. ./tmp/something.js rather than /tmp/somethings.js. Writing to ./tmp is a very reasonable strategy, though. Put the code to write out your bundled / minified assets into your boot cycle (e.g. config/environment.rb, an initializer, etc) and that way you'll only do it once per dyno restart. Dynos are restarted when you push new code, when you type heroku restart, and then periodically (every 12 - 24hrs) otherwise. Adam -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: A conclusive way to package static assets
On Sun, Jul 18, 2010 at 5:44 PM, Julio Cesar julio...@gmail.com wrote: The official docs[1] say: There is no guarantee that this file will be there on subsequent requests (although it might be), so this should not be used for any kind of permanent storage. And you just pointed out: and that way you'll only do it once per dyno restart Your tmp directory does persist as long as your dyno or worker does, generally no less than a couple of hours and no more than a day. This makes it suitable for use to write bundled assets on startup. The docs simplify this a bit by advising developers not to trust that the tmp dir will stay the same between requests. This is true - if dyno #2 handles a request and dyno #4 handles the next one, they'll have different tmp dirs. But it doesn't say anything about the tmp dir's relationship to the lifetime of the dyno or worker process. We should update that since it would be valuable information in this case. Adam -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: wiki for Heroku community?
On Thu, Jul 15, 2010 at 6:50 AM, Maximilian Mack maxm...@gmx.de wrote: Is there a rails wiki software out there who works with heroku? http://github.com/adamwiggins/bitswiki -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: text/cache-manifest MIME type
I put together a small example of an html5 offline app using cache manifest and deployed it to Heroku: http://cachemanifest.heroku.com/ I used the clock example from the html5 draft: http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html Source code: http://github.com/adamwiggins/cachemanifest You can confirm that the manifest is returning the right mimetype like this: $ curl -I http://cachemanifest.heroku.com/clock.manifest HTTP/1.1 200 OK Server: nginx/0.6.39 Date: Thu, 25 Feb 2010 02:53:24 GMT Content-Type: text/cache-manifest ... Visiting the site in firefox 3.5 should ask to allow whether it can store for offline use. Chrome doesn't seem to support this currently, not sure about other browsers. Adam -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: flush memcached?
flush_all isn't possible with the current memcache beta. We've got a major update coming soon that will add support for this. Adam -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: gem bundler support
On Wed, Jan 20, 2010 at 2:58 PM, morgoth w.wnetr...@gmail.com wrote: Great. It works perfectly. One downside: this increase slug size. True. Our experience has been that the many dependency hell issues that can be avoided by explicitly declaring and bundling all your gems is well worth the few MB increase in slug size. Adam -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Temporary Tables - Sqlite in Memory
On Tue, Jan 19, 2010 at 7:24 AM, Karl threadh...@gmail.com wrote: I am thinking of using a temporary table, most likely sqlite in memory table. This will work, but take note it will only work for a single dyno, and the contents of the table will disappear periodically when the dyno is cycled. If you add a worker or a second dyno, now you'll have two in-memory tables which don't match. Adam -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Deploying from rails subdirectory within repository
If you put a config.ru into the root of your project, you can point to
any rack app (including rails) inside of any arbitrary subdirectory.
If you're using rails, this will work:
subdir = File.dirname(__FILE__) + '/my_subdir'
require #{subdir}/config/environment
use Rails::Rack::LogTailer
use Rails::Rack::Static
run ActionController::Dispatcher.new
Just replace my_subdir with the name of your subdirectory.
Adam
--
You received this message because you are subscribed to the Google Groups
Heroku group.
To post to this group, send email to her...@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: do workers use the version of DJ from my app?
It uses the version installed in your codebase. Adam -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: redis+heroku
Yes, I set this up as a demo of scanty-redis a while back: http://scanty-redis.heroku.com/ I put the Redis db on slicehost, described in the third paragraph of this post: http://adam.blog.heroku.com/past/2009/7/13/scanty_on_redis/ Adam -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Filesystem?
On Fri, Dec 18, 2009 at 7:17 AM, iamjediknight iamjedikni...@gmail.com wrote: I have a rails app that reads liquid templates off the filesystem, as well as content (i.e. images, html, etc.). So will I need to store those via Amazon S3? Is there another way to store content? Assuming these things (templates, images) are in your Git repository and you're only reading them, that will work fine. The only time you can't use the filesystem is for writes, such as storing images or pdfs uploaded by your users. For that you should use S3. Adam -- You received this message because you are subscribed to the Google Groups Heroku group. To post to this group, send email to her...@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: Multiple domains pointing to different parts of the application
On Tue, Sep 8, 2009 at 5:33 AM, Jay Godsejgo...@gmail.com wrote:
Is it possible to point
www.d1.com to myapp.heroku.com/a1
www.d2.com to myapp.heroku.com/a2
Yes, although this has more to do with your web framework than Heroku.
Point both domains at your app:
$ heroku domains:add www.d1.com
$ heroku domains:add www.d2.com
If you're using Rails, use a patch like this one:
http://www.smallroomsoftware.com/articles/2007/2/10/rails-routing-based-on-hostname
Then set up your routes to use hostname to route things:
map.connect :controller = 'a1', :conditions = {:hostname = 'www.d1.com'}
map.connect :controller = 'a2', :conditions = {:hostname = 'www.d2.com'}
Personally I think this is likely to result in confusing code, so I
wouldn't do it. But if you want to you that's how you would.
Adam
--~--~-~--~~~---~--~~
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: Site down between Push and Migrate?
On Sun, Aug 16, 2009 at 10:39 AM, Alex Chaffeeale...@gmail.com wrote: During the few seconds the restart is happening, what happens to incoming HTTP requests? Are they queued or do they fail? If the latter, where's the error page and can we change it? And what's the timing like for applying the change to multiple dynos? Is it possible that one dyno is still running the old code while another is running the new code? Requests will always be going to one and only one revision of the code at a time. The sequence is like this: 1. You git push, which compiles a slug. 2. If successful, the slug is distributed to our dyno grid and dynos are started for the new slug. But no traffic is being sent to them yet - the routing mesh is routing all traffic to the dynos running the old slug. 3. Once all the new dynos are up and ready to receive connections, the routing mesh updates its routing table. Existing requests will complete on the old dynos, any new requests will be sent to the new ones. In summary, the switch is instantaneous and seamless, with no period of error pages or requests being routed to the wrong dyno. You can test this yourself by running a simple load test during a deploy. Something like: $ ab -c 1 -n 50 http://myapp.heroku.com/ | egrep '^(Complete|Failed)' $ git push heroku When I ran this I got the following output (after all the git push / heroku slug compile messages): Complete requests: 50 Failed requests:0 Adam --~--~-~--~~~---~--~~ 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: multiple custom domains + wildcards for each?
On Fri, Aug 14, 2009 at 9:24 AM, orlinorlin.mo...@gmail.com wrote: If one app has a couple of custom domain names set, and has wildcards enabled, can I have wildcards turned on just for one of those? Yes. Enabling the add-on only activates the feature for use, you specify domains starting with *. to use it. So for example you might add the following domains to your app: *.example1.com example2.com Here you could access the app via foo.example1.com, but not foo.example2.com. Adam --~--~-~--~~~---~--~~ 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: Passing environment variables to rake
On Thu, Aug 6, 2009 at 11:09 AM, Keenankee...@thebrocks.net wrote: I'm trying to write a rake task that requires additional data command: rake USER=user1 lovdbyless:admin rake file: namespace :lovdbyless do task :admin = :environment do login=ENV['ADMIN'] You need to use ENV['USER'], or else pass ADMIN= on the command line: heroku rake ADMIN=user1 lovdbyless:admin Adam --~--~-~--~~~---~--~~ 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: Full-Text Indexing - How to decide?
On Mon, Jul 27, 2009 at 6:23 PM, Nevilleneville.burn...@gmail.com wrote: Do you have a guide, or blog post perhaps detailing best practice for deploying Solr on Heroku or is EC2 the only way? Solr is a Java program, Heroku only runs Ruby programs. So yes, you need to run it on another server, such as a Slicehost slice, or an EC2 instance (which is preferred since you'll have the lowest latency between your app and Solr.) Adam --~--~-~--~~~---~--~~ 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: Invalid database url for heroku db:push
On Thu, Jul 9, 2009 at 12:46 PM, Sarah Allensa...@ultrasaurus.com wrote: $ heroku db:push Invalid database url development: : *defaults database: mightyverse_dev I think the issue here is that taps turns the database credentials into a URL/URI, and URI.parse considers underscore an invalid character in the database name. I'm not sure why (this is in the path, not the hostname) - perhaps a patch to taps to handle this as a special case would be the workaround. Adam --~--~-~--~~~---~--~~ 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: Root Domain (mydomain.com not www.mydomain.com)?
On Tue, Jul 7, 2009 at 7:25 AM, Ed Jonesed.jo...@gmail.com wrote: C:\Users\Ed\webappshost whendidji.com whendidji.com has address 216.39.57.104 This is your problem. It should read something like this: C:\ host whendidji.com whendidji.com is an alias pointing to proxy.heroku.com Adam --~--~-~--~~~---~--~~ 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: Root Domain (mydomain.com not www.mydomain.com)?
On Mon, Jul 6, 2009 at 7:08 AM, Ed Jonesed.jo...@gmail.com wrote: Alas, for myapp.com, heroku just gives Heroku | No such app. There is no app configured at that hostname. Try: heroku domains:add myapp.com Adam --~--~-~--~~~---~--~~ 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: Config vars and local setup
Very nice, Trevor. I wonder if you could write this up into a blog post somewhere that summarizes the technique? That way we can provide the link to others that prefer not to use environment variables in their local setup. Adam --~--~-~--~~~---~--~~ 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: Varnish Layer
You're correct Jason, 100 varnish servers would mean that fetching a single static asset or cached page could produce up to 100 dyno hits. In practice, I don't think we'd run more than 4 or 5 varnishes in front of a single application - if it became necessary to do that at some point, we'd probably look into switching to Squid, which has the capability to share the same cache pool across servers. In any case, I would be very surprised if the non-shared cache pool between our varnish servers causes you any kind of problem. If it does, of course we'd like to hear about it. Adam --~--~-~--~~~---~--~~ 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: Commit hooks for compiled Sass?
Interesting discussion in that thread, thanks for the link Sean.
At the moment we're not putting any development effort into allowing
user code into the server-side receive hooks, as this has a lot of
deep design and security ramifications that make it a pretty massive
project. I think it's an interesting idea and we'll continue to think
about it, but in the meantime I'd be more interested in seeing other
options. The plugin which compiles the stylesheets on the fly and
caches them in varnish, for example, feels like a better solution to
me - as Ethan put it, an idiomatically appropriate solution.
If you're looking for the absolute easiest way, without changing any
of your app or framework code, the thing to do is put the hook as a
pre-commit on your own Git repo. For example:
$ cat .git/hooks/pre-commit
#!/usr/bin/env ruby
Dir['app/stylesheets/**/*.sass'].each do |sass|
basename = sass.gsub(/app\/stylesheets\//, '').gsub(/\.sass$/, '')
next if basename.match(/^_/) # skip includes
css = public/stylesheets/#{basename}.css
puts Compiling #{sass} - #{css}
system sass #{sass} #{css}
system git add #{css}
end
[Ctrl-D]
$ chmod 755 .git/hooks/pre-commit
Adam
--~--~-~--~~~---~--~~
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: heroku console: ^C should clear, not exit.
On Wed, May 27, 2009 at 1:27 PM, Harry Vangberg ha...@vangberg.name wrote: I didn't realize the heroku console was on GitHub, will take a look at it. http://github.com/heroku/heroku/blob/85693066c72f86595f03ebeae338134b162639d8/lib/heroku/commands/app.rb#L115-128 --~--~-~--~~~---~--~~ 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: Heroku | Backlog too deep
This doc is in the works right now, thanks for giving us a friendly nudge on getting it finished. :) In the meantime, here's a rough cut of the explanation: The backlog is the number of requests waiting to be processed. If you're using the default (one dyno), it can only process one request at a time. This is more than enough for a single user or even a few users. For example, if your app takes 100ms to serve a request, the single dyno can serve 10 requests per second. (This doesn't count static assets or cached pages, which are served straight from Varnish and never touch your dyno.) However, imagine the case where you're getting 15 requests per second. Your single dyno can serve 10 per second (1000ms in a second / 100ms per request = 10 reqs/sec). So after one second you'll have served 10 requests but have 5 in the backlog waiting to be processed. This would be fine if no more requests came in, as those 5 requests would be served in the next 0.5 seconds. However, if you have another 15 requests come in, at the end of the 2nd second you'll have 5 + 15 - 10 = 10 requests in your backlog. After 3 seconds, the backlog will be 15 deep, and so on. If that volume keeps up, the backlog will just keep getting deeper. Eventually, the Heroku routing mesh will detect that you're hopelessly behind, and start turning away some of the requests. You have three options: 1. Increase the number of dynos you have. You can calculate how many you need by taking your average time spent serving a request (100ms in the example above) and multiplying it by how many requests you wish to serve per second. 15 requests per second at 100ms per request would require two dynos. 30 requests per second would require 3 dynos, although you might to go with 4 or even 5 to give yourself a little headroom, since traffic often comes in spikes. 2. Speed up your response time. A performance analysis tool like New Relic is invaluable here. If you're spending more than 100ms in your dyno processing the request, you probably have room for optimization. This is a big topic, but some options here include use of memcached, HTTP caching, optimizing your database queries, or using a faster web layer like Rails Metal. 3. If your traffic is low-value, such that you don't feel it's worth paying for more dynos, then perhaps you are comfortable with turning users away during traffic spikes. In that case, take no action, and be aware that some users will get this error message. Adam --~--~-~--~~~---~--~~ 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: reverting a commit?
In the case where you've edited the commits or reset the HEAD to rewind to an earlier commit, you can force the push like this: $ git push -f heroku Note that if you have other people pulling from the Heroku app, they should probably destroy their master branch and fetch it fresh, to avoid accidentally re-pushing the removed/changed commits. Adam --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
elevated errors today - resolved
Hey folks, we'd been having elevated error rates today (the http 503 / ouchie guy page). They were very intermittent (just reload and the next request would usually work) but still very annoying. We tracked down and resolved the problem, so things should be back to normal now. Adam --~--~-~--~~~---~--~~ 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: Can't use CNAME and MX records together
Another fix for this is to alias your domain to point to proxy.heroku.com instead of heroku.com. i.e.: $ host mydomain.com mydomain.com is an alias for proxy.heroku.com. proxy.heroku.com has address 75.101.145.87 proxy.heroku.com has address 75.101.163.44 Although it reads a little less nicely, this avoids having to tinker with MX records, so perhaps we'll make this the official way to set up custom domains. What do you guys think? Adam --~--~-~--~~~---~--~~ 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: Other branch - other URL ?
On Fri, Apr 24, 2009 at 7:51 AM, Damien MATHIEU kaz...@gmail.com wrote: When I work on a new feature for my application, I do it in a specific branch; I commit in that branch. [...] For example, have xxx.heroku.com on the branch master of the application xxx. And yyy.xxx.heroku.com on the branch yyy of the same application. If I'm understanding you correctly, you should be able to do this with two different remotes, and using git's syntax to pushing to a specific branch on the remote. Assuming that you have branches master and experimental, for example: heroku create myapp-experimental --remote app2 git checkout experimental git push app2 master That will push whatever the current branch is, in this case experimental, to the master branch on Heroku. Adam --~--~-~--~~~---~--~~ 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: newbie question on what to do after change url
Try this: git remote rm heroku git remote add heroku g...@heroku.com:followme.git Adam --~--~-~--~~~---~--~~ 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: how do I find out how much space I have?
We're working on providing a lot of information about exactly what resources your app is using. The first small step toward this is that heroku info will now show some stats about your code and data size: $ heroku info --app adamblog === adamblog Web URL:http://adamblog.heroku.com/ Git Repo: g...@heroku.com:adamblog.git Repo size: 876k Slug size: 704k Data size: 360k in 1 table If you're running latest client gem (0.8) and you don't see one or more of these fields, it's because it's still being calculated. In the case of repo/slug size, you may not see them until you push your code again. Adam --~--~-~--~~~---~--~~ 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: db problems today and where to find heroku status/outage info
Guys - We had some system-wide downtime today, as described in this thread. We know that downtime is definitely in the not awesome, not at all category. Heroku is hitting some serious growth right now. Up until now we've been focusing all our efforts on making a really seamless deployment workflow. I think we've pretty much nailed that (though of course there's 1001 features we can't wait to add), so now we're turning our attention to scaling to meet the new load and general operational stability. As we work on stuff like building a status page (yeah I know, it's long overdue) and all the ops stuff that you do to chase that holy grail of 100% uptime, we're gonna hit a few growing pains such as today's little escapade. We appreciate your bearing with us as we continue to mature our product and our operation. Adam --~--~-~--~~~---~--~~ 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: Subdomain CNAMEs
You've stumbled upon a beta feature that is not yet publicly available. Drop me a private email if you'd like access to this. Adam --~--~-~--~~~---~--~~ 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: Failed to push mysql db when installing Radiant
Tony, can you run sudo gem install taps to get the latest version (Ricardo has been hard at work fixing numerous edge-case bugs), and then try again? If you still get an error, post the exact output here. Adam --~--~-~--~~~---~--~~ 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: Internal server error when trying to execute anything in the console
Should be fixed now. Adam --~--~-~--~~~---~--~~ 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: no error message detail
Timeouts are tricky to debug. One option could be an infinite loop, or hitting a remote service on startup that is slow or taking a long time. Another possibility would be something like building a big index, which may not run infinitely, but if it takes more than 20 seconds we assume a timeout. Even having a huge quantity of plugins that need to be initialized can sometimes create very long boot times. One thing to try is heroku restart, which will take another pass at trying to boot, and if the timing issue is intermittent, it might work the second time around. Adam --~--~-~--~~~---~--~~ 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: Internal Server Error on db:data:load
Yes, db:push is a preferred method, if you have the database loaded locally. Make sure you have the latest version of the heroku and taps gems installed: sudo gem install heroku taps ...and then read details here: http://docs.heroku.com/taps Adam --~--~-~--~~~---~--~~ 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: root CNAME with slicehost DNS
One reason this can happen is that the DNS info was cached on the local nameserver prior to it propagating from your provider (Slicehost, in this case). In that case you have to wait about 20 minutes for the cache to clear. Can you try it again right now and let me know if it works? We've got some ideas for how to work around this, it's definitely a point of confusion/annoyance when setting up domains. Adam --~--~-~--~~~---~--~~ 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: Multiple domains pointing to heroku app?
You can do multiple domains on Heroku via the command-line tool: heroku domains:add mydomain1.com heroku domains:add mydomain2.com See: http://docs.heroku.com/custom-domains#heroku-setup Adam --~--~-~--~~~---~--~~ 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: Internal Server Error
We had a brief issue with one git server this morning. It's fixed now - try your push again. Adam --~--~-~--~~~---~--~~ 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: Can't install heroku gem?
That's very odd. Github downtime shouldn't affect the Heroku gem, since it's in Rubyforge. Can you type gem sources and see if it lists http://gems.rubyforge.org? Adam --~--~-~--~~~---~--~~ 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: db:pull doesn't work (uses wrong socket)
In addition to Ricardo's solution, I think another thing you can do is just leave off the database url. You mentioned that you have a config/database.yml, without specifying a URL it will read from that automatically. i.e. $ heroku db:pull Auto-detected local database: sqlite://db/development.sqlite3 ... Adam --~--~-~--~~~---~--~~ 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: curl from heroku
You can use curl, via the backticks you suggested. However, it would be more portable to do it with pure Ruby, using a library such as RestClient, HTTParty, or good ol' fashioned Net::HTTP. Adam --~--~-~--~~~---~--~~ 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: getting started test database is not configured
Heroku doesn't provide a test database, so heroku rake test won't work. This might be an interesting feature to provide at some point, although automated CI systems like runcoderun.com may be a better approach than trying to run tests on a production system. If you're just tinkering with a new app, one thing to try is heroku console. This will let you run methods and see if it seems like everything is working the way you expect. Adam --~--~-~--~~~---~--~~ 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: Data.yml exported from HerokuGarden is out of date.
I ran a manual db:data:dump for saps.herokugarden.com. You should be able to download the file now. Adam --~--~-~--~~~---~--~~ 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: rest_client , external web services
On Sun, Mar 22, 2009 at 3:21 PM, pabloa pablo.flo...@gmail.com wrote: hi, i am using the rest client gem to connect to a public dictionary web service via a HTTP GET, but it seems that Heroku does not allow this connection . All Heroku apps can send traffic on the web ports (80 and 443), so this should work. Post your code (minus any http auth data or other sensitive info) and perhaps someone can spot the issue with it. Adam --~--~-~--~~~---~--~~ 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: i some ssh issue
Post the contents of your .git/config - maybe your git remote is wrong. Note that the host portion should be g...@heroku.com, not heroku.com. Adam --~--~-~--~~~---~--~~ 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: Problem moving from herokugarden - rake aborted! Don't know how to build task 'db:data:load'
On Mon, Mar 23, 2009 at 2:40 PM, ptorrsmith ptorrsm...@gmail.com wrote: $ sudo apt-get install git This should be: sudo apt-get install git-core It's definitely confusing that there is a package named git on Debian which is not the Git revision control system. Adam --~--~-~--~~~---~--~~ 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: Rails 2.3 support
One catch here - make sure you're running on heroku.com. herokugarden.comdoes not have Rails 2.3 installed. Adam --~--~-~--~~~---~--~~ 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: Problem launching app us github gem (mislav's will paginate) via .gems
I get this same error running locally. I was able to fix it by changing this line: On Sun, Mar 15, 2009 at 12:00 PM, Nick Dimiduk ndimi...@gmail.com wrote: config.gem 'mislav-will_paginate', :version = '~ 2.2.3', :lib = 'will_paginate', :source = 'http://gems.github.com' ...to read like this: config.gem 'mislav-will_paginate', :version = '= 2.2.3', :lib = 'will_paginate', :source = 'http://gems.github.com' Since the latest version of mislav-will_paginate is 2.2.8, specifying = 2.2.3 means that that will work. (Your other option would be to specify the exact gem version of 2.2.3 in your .gems.) Adam --~--~-~--~~~---~--~~ 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: Data.yml exported from HerokuGarden is out of date.
We disabled yamldb output on export because it was causing http timeouts. I installed the yaml_db plugin in your app and manually ran rake db:data:dump, so now db/data.yml should be the latest version. If you have any trouble downloading it, email me privately and I'll email it to you. If anyone else is having trouble getting their data out of Heroku Garden, contact me. Adam --~--~-~--~~~---~--~~ 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: github vs. heroku vs. rubyforge
Great question David: On Thu, Mar 12, 2009 at 9:33 AM, David Rogers david.t.rog...@gmail.com wrote: - gems are at home at rubyforge. - apps are at home in heroku. - open collaboration's home is github. Does establishing and updating git repos at all three make sense? Yes, absolutely. The way I usually set things up for my open source apps - for example, Rifgraf and Scanty - is to have a remote named github which pushes to github and another named heroku that deploys to Heroku. Having no origin means that git push won't do anything - I have to explicitly say which I want, which I think is best given that one remote puts my code up for public viewing and the other deploys a live app. I typically don't bother using Rubyforge's SCM (I see it as a repo for packages, not code trees), but you certainly could push a mirror of your github code to rubyforge very easily if you like doing that. Adam --~--~-~--~~~---~--~~ 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: Sprockets
On Thu, Mar 12, 2009 at 1:08 PM, Kris S forward.f...@gmail.com wrote: Is it possible to use sprockets with in an app on heroku? It writes out a js file, and for this reason I am not sure if its permitted or not. You'll need to compile the sprockets and commit the file to the repository for this to work - the rake task won't work on Heroku, because of the read-only filesystem. This is the same deal as Sass files - anything that needs to be compiled must be done beforehand. Max had an interesting idea for how we could do this during the slug compile: http://groups.google.com/group/heroku/msg/df0aadd4307beb08 But we're still pondering whether this will be feasible, so in the meantime keep the compiled files in your repo. Adam --~--~-~--~~~---~--~~ 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: Ready for Production? Questions
On Thu, Mar 12, 2009 at 8:42 AM, K2 ke...@coderow.com wrote: 1. What will the eventual cost structure be? I know you don't want to release exact pricing, but will it be more inline with EngineYard's Solo or Mor.ph's AppSpace? ~$50-$250 month for most apps. Or more of the Mor.ph App Cloud offering starting in the $1500/month space? I really don't want to deploy here, and then find out I can't afford it. I can't say much here, but I can assure you that you'll be able to afford it. The lowest offering will probably be in the two-digit range, though the higher ones will certainly go to four digits. 2. Database backups: I know there are rake tasks to get a local DB dump, but I haven't heard much about what you suggest as best practice for DB backups especially what we should do vs. what you are doing as part of the environment itself. We're still refining our thinking on best practices here. There are many layers of redundancy counting both Amazon's infrastructure and ours; but as with any service, keeping your own backups of important data is an extremely good idea. One way you can do that right now is set up a local cron job from your workstation to capture and download a bundle every night. For example: 30 01 * * * cd ~/myapp; heroku bundles:capture; sleep 60; heroku bundles:download We have another feature related to database backups in beta right now, contact us if you'd like to participate, otherwise watch the blog for the announcement. 3. Memcache: I haven't seen anything in the docs for the configuration for this. I see the Varnish info, but not memcache. I assume that Heroku is configuring memcache automatically and we just need to worry about the app-specific cache retrieve/expire calls. Good eye! The diagram is speculative on that particular point - we have memcache in beta but haven't documented / released it publicly yet. Once again, contact us for the beta, or wait for the announcement. 4. General Release: I know you don't want to release a date yet, but is this weeks or months away? Will a range suit you? :) It's more than a week, but probably less than four months. Adam --~--~-~--~~~---~--~~ 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: User Agent not possible on heroku?
Don't store things on the filesystem - because your app is spread across the dyno grid, there's no guarantee that something written to the tmp directory will be there on the next request. The place for permanent data storage is the database. If you wish to do a curl-style cookiejar to keep a session on a remote site, create a table in the database (perhaps remote_cookies or remote_sessions?) to store this info. Adam --~--~-~--~~~---~--~~ 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: New App on Heroku not working
On Thu, Mar 5, 2009 at 11:21 PM, DAZ daz4...@gmail.com wrote: Here is my development.rb file, I can't see any reference to cache_template_loading, is the line I need to remove here? Oops, sorry - it's actually config/environments/production.rb, line 13. As someone else pointed out, Heroku runs in production mode. It was probably working on Garden because it was running in development mode there. Adam --~--~-~--~~~---~--~~ 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: Problems with pids
Felix - We don't support background processes run this way, as it's not compatible with a cloud architecture. See http://heroku.com/how/dyno_grid for some background on this. We're currently working on a feature to support background jobs in a cloud-friendly way. It would be helpful if you could tell me more about exactly what you're trying to do, so that we can include your requirements into our design. Adam On Mon, Mar 2, 2009 at 3:20 PM, Felix Holmgren felix.holmg...@gmail.com wrote: I'm spawning a couple of background processes in my Rails app, and have inserted checks to see if old processes (possibly from earlier runs of the app) are still around. If there are old processes, the app either kills them or lets them carry on with their work and desists from spawning even more processes. I use something like Process.kill(0, pid) to check if old processes are still alive. Unfortunately, on the Heroku server this call always indicates that the process is dead. In short, I have no access to processes that I once spawned, although I have their pid stored in the db. I can neither kill them nor reliably find out if they are alive. This has lead to situations where I had to redeploy to a new Heroku process to get rid of background processes hanging around in the background. For my app to work, I simply need to be able to spawn, track and kill processes. Is there a workaround, or do you envision one for the future? I understand there are various security considerations, but it's not that complicated: let processes with the same uid do what they will with each other. For now, I've had to move back my app to my old server, which is otherwise so much less sexy than Heroku. Felix --~--~-~--~~~---~--~~ 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: App just coming up with black bar
This is the page that serves the crashlog, but for some reason there was no log. Definitely would like to find out what happened there, but it seems like it came back on its own. In any case, a heroku restart will probably always fix something like this. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Server failing to start
On Sat, Nov 29, 2008 at 3:46 PM, Corey Haines [EMAIL PROTECTED] wrote: The server for feedmyworms failed to start. Details: /usr/lib/ruby/gems/1.8/gems/rails-2.2.2/lib/initializer.rb:530:in `send': undefined method `cache_template_loading=' for ActionView::Base:Class (NoMethodError) from Since we installed the 2.2 gem, a lot of people seem to be hitting this. In every case I've seen, it's because the app is expecting 2.1, but this isn't explicitly specified in the environment. Add this to config/environment.rb to avoid this problem: RAILS_GEM_VERSION = '2.1' Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Migrations not auto-running on new 2.2.2 deploy
Good catch. This should be fixed soon; in the meantime, you can always run migrations manually at the command line, i.e. $ heroku rake db:migrate Adam On Thu, Nov 27, 2008 at 10:45 AM, Matthew Moore [EMAIL PROTECTED] wrote: When I run through these steps on my new 2.2.2 app I'm deploying, the migration run seems to fail. However, I can edit the app in heroku, and run the migrations from the edit screens in Firefox, and they run just fine. I didn't have this problem a week ago when I deployed another app using 2.1 on heroku, so I'm not sure if that's the culprit. $ heroku create name-and-logo-footer Created http://name-and-logo-footer.heroku.com/ | [EMAIL PROTECTED]:name- and-logo-footer.git $ git remote add heroku [EMAIL PROTECTED]:name-and-logo-footer.git $ git push -f heroku Counting objects: 115, done. Compressing objects: 100% (106/106), done. Writing objects: 100% (115/115), 86.76 KiB, done. Total 115 (delta 28), reused 0 (delta 0) refs/heads/master: eda560e8ba076e185b5caac56d141874eb41376f - 9ffa68a2a43f3e4a091ee6bca2682e41db6d06b4 To [EMAIL PROTECTED]:name-and-logo-footer.git + eda560e...9ffa68a master - master (forced update) HEAD is now at 9ffa68a... heroku prep Running migrations... rake aborted! No such file or directory - /mnt/home/userapps/43197/config/ database.yml --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Rails 2.2
As promised, the Rails 2.2 is now available for use for all apps on Heroku: http://blog.heroku.com/archives/2008/11/26/25_rails_2_2_on_heroku/ Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: 2.1.2 version
Although 2.1.0 will work, I highly suggest leaving off the minor version number: RAILS_GEM_VERSION = '2.1' This will allow your app to work with whatever minor version is installed wherever you a running it. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Creating apps seems to have 'issues'
Is this still happening now? Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: 504 Gateway Time-out
Fixed. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Bandwidth Limits
This is a sweet app Nathan, nice job! We can definitely crank your bandwidth limits and do some other things to make sure you're fully available on election day. I'll reply to you off-list about the details. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: App Overlimit
I've cleared the overlimit flag, so you're back up. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: how do you collapse git revision history?
You can run git's garbage collector like so: git gc This often reduces a repository size significantly. Another option is to rebase and remove commits of large binary files that have since been removed, but are still stored in the history. Run git gc afterward to clean it out. There's also the simple and extreme clean sweep: of rm -r'ing your .git dir and starting with a fresh git init. In your case Jeremy, I believe you're creating a fresh repo on every push, so there won't be any history to clean up. So then the next best thing to do is look for large files you can remove, like photoshop mockups, binary libraries, etc. After that, if you still are over quota, the best thing to do is email us privately and we'll see what we can do. :) Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Git - Internal server error - fatal: The remote end hung up unexpectedly
timesonline is fixed. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: New, small app over limit in error
Your app went overlimit on bandwidth, although this reset at midnight so you're already back. I blessed the app which will give you plenty of headroom so you shouldn't hit this again. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: git push and Gateway Timeout problems
Fixed, there were both the same issue. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: deployment issue with git push
My guess is that some of your plugins were installed via git clone, and so contain a .git directory inside them on your local machine. This will cause git to skip over them when adding to the top-level repository, and thus they won't be pushed to Heroku. You can test this theory with a command like this: find . -name .git If it shows more than one line, then you've got extra git repos. You can fix it like this: rm -r `find . -mindepth 2 -name .git` git add . git commit -m add git cloned plugins Then you can push to Heroku. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: download large file
I've blessed your app, which will give you plenty of headroom on bandwidth, and cleared the overlimit flag for the day. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: quote_table_name adjustment
Thanks for the heads-up. Better yet, how about sending a pull request with your patch? - http://github.com/adamwiggins/yaml_db Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: initializing and updating git submodules
I highly recommend switching to cookie store sessions, i.e. put
something like this in your environment.rb:
config.action_controller.session = {
:session_key = '_myapp_session',
:secret =
'2cdb95d5605cdd6fadebe717b26f08a12587aaf1635794be192b0dfaedf36c20ef0512e10f577e068fa679db5620b7cd0d45b1f671095f27a6f3debab2ac5d58'
}
Then you won't need to worry about managing your database sessions at
all. (Change the secret to some other long hex key prior to inserting
into your app.)
Adam
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en
-~--~~~~--~~--~--~---
Re: Multiple GIT repositories + project in a subdirectory...
One workaround you could use would be to make a rake task or shell script which creates a temporary git repo for the purpose of deploying. Something like this: cd subproj git init git add . git commit -m 'bundle for heroku deploy' git remote add heroku [EMAIL PROTECTED]:myapp.git git push -f heroku rm -rf .git This will make for a slower deploy since it's pushing the entire repo each time, but the difference will only be a few extra seconds unless you have a huge revision history. On another note, I would encourage you to consider switching to a one repo per app, if that's at all feasible for you. I've tried it both ways and my experience is that one repo per app makes for a much better separation of concerns. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Mongrel Not Starting
These seem to have corrected themselves, with the exception of jactwedding - I restarted the Thin and that brought it back. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Can't edit my app
Fixed. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Can't edit my app
Fixed. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Can't edit my app
Just fixed one other thing that was affecting some apps (different issue from the first one). If you're still having trouble, reply, and please remember to include the name of your app. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
API update
New client gem / API released today, now in Rubyforge (gem install heroku to update). New features: - Manage sharing (add/remove/list collaborators) - Manage multiple ssh keys for your user (add/remove/list keys) - Update settings (public true/false, mode production/development) - Rename an app - Run rake tasks remotely Full post to our blog, which we're going to start using for news announcements again: http://blog.heroku.com/archives/2008/9/3/heroku_api_update/ Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: Heroku could be the ultimate publishing tool for Rails bloggers and gem/plugin developers
Thanks Paul, we're glad you like Heroku so much. I totally agree that the possibilities for broader collaboration are really exciting - we have tons of ideas for this, some of which are already in the works. At the moment we're mostly focused on stabilizing the platform, but we're really looking forward to being able to work on collaboration and other advanced features in the near future. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: About merb
Small apps will always be free, and medium apps will be affordable to individuals and small companies. So don't worry on that front. As to running Merb or other frameworks besides Rails, you can't do it today, but it is something we've considered. Quick straw poll: who else is interested in being able to run Merb, or some other Ruby framework, on Heroku? Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
Re: How do I connect to an external database?
Connecting to external databases is probably not a good idea. It may or may not work now, but I suspect it will definitely not work in the future after we make some other architectural changes we have in mind to facilitate scaling. I'd recommend rethinking your application architecture to follow modern conventions, i.e. changing the external database access into REST calls to an app that is directly connected to that database. I realize that might seem like a big change, but it might also be easier than you think. If you post some of the specifics (like a description of what your app is doing, or even code snippets) I or someone else here might be able to advise you on this. Adam --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~--~~~~--~~--~--~---
