Re: Could an admin add a subject prefix to this list, like [heroku]
I think what Richard is saying is there is no reason to force a change on every user, when a less intrusive (filters) method exists. On May 11, 2011 3:36 PM, "Travis Reeder" wrote: > I get the filter thing can work, but how about not making everyone on the > list create a filter when one person can do it once for the entire list. I > don't think the reasons you present are very compelling reasons to not do > it. Subject line noise is most welcome when it tells me what list it's from > (like your labels) and how does it prevent you from identifying old messages > visually? > > Not meaning to start a big discussion here, just seems like an odd response > to a request for something so common. > > On Wed, May 11, 2011 at 3:20 PM, Richard Conroy wrote: > >> There is usually good reason why lists don't prefix. Line noise on the >> subject line being one of them, also the availability of advanced e-mail >> clients that can do powerful filtering. >> >> For instance, in GMail, which both of you use, I can set a filter to label >> all my Heroku posts. >> >> Hence, subject prefixing becomes redundant, and also very irritating when >> you are trying to identify old messages visually. >> >> regards, >> Richard >> >> >> On Wed, May 11, 2011 at 11:07 PM, Miles Smith wrote: >> >>> I second this. >>> On May 11, 2011 10:54 AM, "Travis Reeder" wrote: >>> > So we can know what list it is without having to open the email. >>> > >>> > Cheers. >>> > >>> > -- >>> > 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. >>> > >>> >>> -- >>> 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. >>> >> >> >> >> -- >> http://richardconroy.blogspot.com | http://twitter.com/RichardConroy >> >> -- >> 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. >> > > -- > 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. > -- 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: Could an admin add a subject prefix to this list, like [heroku]
Well look who slept at a holiday inn express last night! Thanks for the tip Richard. On May 11, 2011 3:20 PM, "Richard Conroy" wrote: > There is usually good reason why lists don't prefix. Line noise on the > subject line being one of them, also the availability of advanced e-mail > clients that can do powerful filtering. > > For instance, in GMail, which both of you use, I can set a filter to label > all my Heroku posts. > > Hence, subject prefixing becomes redundant, and also very irritating when > you are trying to identify old messages visually. > > regards, > Richard > > On Wed, May 11, 2011 at 11:07 PM, Miles Smith wrote: > >> I second this. >> On May 11, 2011 10:54 AM, "Travis Reeder" wrote: >> > So we can know what list it is without having to open the email. >> > >> > Cheers. >> > >> > -- >> > 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. >> > >> >> -- >> 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. >> > > > > -- > http://richardconroy.blogspot.com | http://twitter.com/RichardConroy > > -- > 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. > -- 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: Could an admin add a subject prefix to this list, like [heroku]
I second this. On May 11, 2011 10:54 AM, "Travis Reeder" wrote: > So we can know what list it is without having to open the email. > > Cheers. > > -- > 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. > -- 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: IDE?
Actually, If you stored the files in a redis/memcached solution, and then pushed them to S3, it could technically work. Not sure how well though... On Sun, Mar 13, 2011 at 7:21 PM, Keenan Brock wrote: > It was moved to herokugarden.com, but alas. It is no longer with us. > > > And if you guys don't bring back the service from the dead, I'd love to see > how the source worked on the back end. > Could you host something like that on Heroku? > Guess it would probably need a read/write file system. > > --Keenan > > > On Mar 13, 2011, at 4:03 PM, szh wrote: > > > I heard that there used to be a Heroku editor so you could actually make > your apps in the cloud too. Are there any plans to bring that back? > > > > -- > > 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. > > -- > 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. > > -- 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: Dyno wake up processing
I always assume my cronies is running brand new instances. Why not just check if you files are there, if not , create them. On Mar 8, 2011 3:39 AM, "Wes Gamble" wrote: > Given a Heroku app.: > > If I have a cron job that populates a cache directory in RAILS_ROOT/tmp > once a day, and all of my dynos go idle, when they "wake up", will the > "tmp" directory be empty or will it still contain what my cron job wrote? > > (I think the deeper question here is whether a dyno "wakes up" in some > pre-existing state, or whether a dyno. is simply reconstituted from the > slug state at deploy-time? I apologize if my phrasing is > awkward/imprecise.) > > If "tmp" will be empty, do we have any way to hook into the "dyno > wake-up process" in order to do some filesystem initialization in /tmp? > > Thanks, > Wes > > -- > 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. > -- 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: amazon simple email service + heroku
How does one remove themselves from the sandbox? On Fri, Feb 4, 2011 at 9:51 AM, Dan Croak wrote: > That doesn't appear to be true once you've moved out of their sandbox and > into the production environment. I just tested this a few seconds ago, > sending an email via Amazon SES from a Rails app to an email that has never > received an SES email before. > > The user received only the email from my app, no opt-in email from Amazon. > > On Fri, Feb 4, 2011 at 12:21 PM, Miles Smith wrote: > >> I've tried SES and it has an extremely crippling requirement: >> >> Every email must opt-in to recieve an email from SES. If you attempt to >> authorize an email account, Amazon sends out a very non-descriptive, cryptic >> (for normal users) message that states that "Amazon SES would like to send >> email to you". It doesn't say anything about my app, nor did I find any way >> of modifying the message that's sent. >> >> Still not ready to replace my current email solution with them for that. >> :( >> >> On Fri, Feb 4, 2011 at 8:21 AM, Tim Fletcher wrote: >> >>> > 2) Any sign of a Ruby library? >>> > Currently only .NET, Java and PHP wrappers. >>> >>> Yes, there's one here: >>>https://github.com/drewblas/aws-ses >>> >>> This might help if you're using Rails 3: >>> >>> http://robots.thoughtbot.com/post/3105121049/delivering-email-with-amazon-ses-in-a-rails-3-app >>> >>> Cheers, >>> Tim >>> >>> -- >>> 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. >>> >>> >> >> >> -- >> >> >> Miles Smith >> *Owner/Lead Developer* >> http://vimae.com/ >> >> This e-mail and any files transmitted with it are confidential and >> intended solely for the use of the individual or individuals to whom the >> e-mail is addressed. This e-mail and any files transmitted with it may >> contain confidential, proprietary or legally privileged information. No >> confidentiality or privilege is waived or lost by any mistransmission. If >> you are not the intended recipient of this e-mail, please immediately notify >> the sender and delete and/or destroy the e-mail (along with any files >> transmitted with it) and all electronic or hard copies from your system. You >> should not, directly or indirectly, use, disclose, distribute, print, or >> copy any part of this message if you are not the intended recipient. >> >> -- >> 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. >> > > -- > 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. > -- Miles Smith *Owner/Lead Developer* http://vimae.com/ This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or individuals to whom the e-mail is addressed. This e-mail and any files transmitted with it may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient of this e-mail, please immediately notify the sender and delete and/or destroy the e-mail (along with any files transmitted with it) and all electronic or hard copies from your system. You should not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. -- 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: amazon simple email service + heroku
I've tried SES and it has an extremely crippling requirement: Every email must opt-in to recieve an email from SES. If you attempt to authorize an email account, Amazon sends out a very non-descriptive, cryptic (for normal users) message that states that "Amazon SES would like to send email to you". It doesn't say anything about my app, nor did I find any way of modifying the message that's sent. Still not ready to replace my current email solution with them for that. :( On Fri, Feb 4, 2011 at 8:21 AM, Tim Fletcher wrote: > > 2) Any sign of a Ruby library? > > Currently only .NET, Java and PHP wrappers. > > Yes, there's one here: >https://github.com/drewblas/aws-ses > > This might help if you're using Rails 3: > > http://robots.thoughtbot.com/post/3105121049/delivering-email-with-amazon-ses-in-a-rails-3-app > > Cheers, > Tim > > -- > 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. > > -- Miles Smith *Owner/Lead Developer* http://vimae.com/ This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or individuals to whom the e-mail is addressed. This e-mail and any files transmitted with it may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient of this e-mail, please immediately notify the sender and delete and/or destroy the e-mail (along with any files transmitted with it) and all electronic or hard copies from your system. You should not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. -- 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: Downgrading newrelic
Try heroku addons:upgrade newrelic:silver Kindof opposite of what you'd think, but that's the way to do it. On Jan 30, 2011 7:17 AM, "Helder Ribeiro" wrote: > I'm using NewRelic Gold right now, and want to downgrade to Silver. If I do > > heroku addons:add newrelic:silver > > does that downgrade the same account (preserving data), or do I have to > remove the gold addon and then add the silver? > > Thanks, > Helder > > -- > 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. > -- 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.
Dalli Gem on Snow Leopard
So, I'm trying to develop my site on my mac (Snow Leopard), and I'm having
trouble with the Dalli gem: See the output below:
< 4:00PM> ~/code/mcserverlist-heroku :git => master, :ruby =>
|➜ irb
>> require 'dalli'
=> true
>> dc = Dalli::Client.new
=> #0}>
>> dc.flush
I, [2011-01-20T16:01:13.955093 #7663] INFO -- : localhost:11211 failed (count:
0)
I, [2011-01-20T16:01:14.465918 #7663] INFO -- : localhost:11211 failed (count:
1)
W, [2011-01-20T16:01:14.466363 #7663] WARN -- : localhost:11211 is down
Dalli::NetworkError: localhost:11211 is down: Timeout::Error IO timeout
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/server.rb:41:in
`request'
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/options.rb:14:in
`request'
from
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/monitor.rb:242:in
`synchronize'
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/options.rb:13:in
`request'
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/client.rb:144:in
`flush'
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/client.rb:144:in
`map'
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/client.rb:144:in
`flush'
from (irb):3
>> dc.set('test', 1)
I, [2011-01-20T16:01:22.442959 #7663] INFO -- : localhost:11211 failed (count:
2)
Dalli::RingError: No server available
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/ring.rb:45:in
`server_for_key'
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/client.rb:224:in
`perform'
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/client.rb:111:in
`set'
from (irb):4
>> dc.get('test')
I, [2011-01-20T16:01:27.298276 #7663] INFO -- : localhost:11211 failed (count:
3)
Dalli::RingError: No server available
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/ring.rb:45:in
`server_for_key'
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/client.rb:224:in
`perform'
from /Library/Ruby/Gems/1.8/gems/dalli-1.0.1/lib/dalli/client.rb:46:in
`get'
from (irb):5
>> require 'memcached'
=> true
>> m = Memcached.new
=> #,
@struct=#, @default_ttl=604800,
@options={:rcv_timeout=>0.25, :binary_protocol=>false,
:exceptions_to_retry=>[Memcached::ServerIsMarkedDead,
Memcached::ATimeoutOccurred, Memcached::ConnectionBindFailure,
Memcached::ConnectionFailure, Memcached::ConnectionSocketCreateFailure,
Memcached::Failure, Memcached::MemoryAllocationFailure, Memcached::ReadFailure,
Memcached::ServerError, Memcached::SystemError, Memcached::UnknownReadFailure,
Memcached::WriteFailure], :noreply=>false, :timeout=>0.25,
:prefix_delimiter=>"", :hash_with_prefix_key=>true, :no_block=>false,
:server_failure_limit=>2, :credentials=>nil, :distribution=>:consistent_ketama,
:ketama_weighted=>true, :default_ttl=>604800, :auto_eject_hosts=>true,
:support_cas=>false, :poll_timeout=>0.25, :default_weight=>8,
:buffer_requests=>false, :hash=>:fnv1_32, :connect_timeout=>4,
:verify_key=>true, :experimental_features=>false, :tcp_nodelay=>false,
:retry_timeout=>30, :use_udp=>false, :exception_retry_limit=>5,
:cache_lookups=>true, :show_backtraces=>false, :sort_hosts=>false},
@not_stored=#>
>> m.flush
=> nil
>> m.set('test', 1)
=> nil
>> m.get('test')
=> 1
>>
As you can see, the Memcached gem works perfectly, however Dalli does not.
Since Dalli is the prefered method for heroku, can anyone help me out with
what's going wrong here?
Miles Smith
mi...@vimae.com
--
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.
