Well, lo and behold, its working -- on the Aspen stack, no less! The
trick was to keep the code block in the controller or model the action
was being called from.
The only thing not working at this point is adding a worker when one
is already running.
heroku.set_workers(ENV['HEROKU_APP'], +1) se
I would submit a ticket, but I get
Oh no.
Something went wrong.
from Zendesk when I click on the support button.
I'm supposed to have a cron running, but if I run
heroku logs:cron --artcal-production
I get no output at all.
--
You received this message because you are subscribed to the Googl
Instructions for requesting production access are here:
http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/index.html?InitialSetup.Customer.html
About three minutes after we submitted the form requesting access, an actual
human from Amazon called us to verify. By the time we hung up the
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 Ra
The only problem we've seen so far is not being able to use the Reply-To
header because THAT email address must be verified:
https://forums.aws.amazon.com/thread.jspa?messageID=220892
That's the typical pattern where your app always sends email (never on
behalf of another user), but you set the "
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, n
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
> 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 might also want to check out RackRewrite which has lots of great features.
On Feb 4, 2011, at 2:45 AM, John Beynon wrote:
> yep, it's redirect inside routes is a 301 redirect by default -
>
> https://github.com/rails/rails/blob/master/actionpack/lib/action_dispatch/routing/redirection.rb
>
i think this is something for the integrity forum, as not many people here
have tried it. (and the issues we're having are not standard rails app
issues).
Let me know if you get an answer from the integrity people, as I'd like to
see this working too.
-John
On Fri, Feb 4, 2011 at 2:26 AM, Amit K
Hi,
Any updates on this?
On Thu, Feb 3, 2011 at 5:21 PM, Amit Kulkarni wrote:
> Yes we cannot use ssh keys because of which i am using the https url.But
> again it is not working and getting the error
>
> I tried to clone the private repo on my local machine using the https and
> it is asking for
11 matches
Mail list logo
