or Create a profile
17 Apr, 2012 11:56 AM
we tried to deploy from S3 yesterday. The deployment failed,
complaining about a missing memcached.yml. After a
lot of debugging, we found out that we provided
the wrong URL for the deployment—the bucket had a policy
requiring secureTransport: true while we typed in the
An error message like "Can't download app tarball from http://..." would have saved us a lot of time.
(Apparently, s3curl does not report errors by default.
That resulted in an XML response from S3 being written to disk
which in turn was unzipped during deployment.)
Formatting help /
(switch to plain text)
(switch to Markdown)
You can attach files up to 10MB
If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.
1 person watching.
A conversation has been started with the Peritor Scalarium staff to resolve this discussion.
This discussion is private.
Only you and Peritor Scalarium support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
Powered by Tender™.