Does this mean it'd be waste of time to write up my "let me tell you about my favorite database" story as part of an application for a job at compose.io ? (serious question)
Good writeup for your experience with Rails and EBS.
I've built my project, Zejoop dot com, in Java/Groovy/Grails and deployed on AWS Elastic BeanStalk - and I'm very happy with my setup so far.
As for your comment about the multitude of services available on AWS, I agree. They've recently added ACM certificate manager which simplified my maintenance considerably.
Their ACM easy implementation probably saved me at least 20 hours of cert renewal agony, plus it was free!
Thanks for looking, and I agree with your assessment. I'm no designer, and only a novice developer. I have a friend who is helping me address weaknesses by designing UI/UX for eventual package as iOs app. I checked your guide; that may be helpful as well. Your feedback /help is appreciated. Will fix.
...seems like pretty basic advice, but I find it very helpful - thanks for making this comment; my own project, zejoop dot com would benefit from a landing page makeover along these lines. I have struggled with this (a clear landing page and CTA) so, a straightforward, easy-to-implement formula helps. Thanks!
I figured out my own mistakes: [1] the actual name was 'Default-Environment', and [2] I had used the wrong zone when I set up AWS CLI using the 'aws configure' command. Fixed both mistakes and zejoop dot com is back online with a working SSL Cert.
Guide is great, except my environment (which can't be renamed) is "My First Elastic BeanStalk Application" - this results in error on CLI "Value 'My First Elastic BeanStalk Application' at 'environmentName' failed to satisfy constraint: Member must have length less than or equal to 23"... stuck
Thanks for documenting that! Now if I could only remember where I put my I put my 'AWS Access Key ID' and its corresponding 'AWS Secret Access Key' so that I could 'aws configure' from the CLI I'd be golden! The guide looks great though.
Thanks, I will investigate. Not clear though if I'll need to convert the cert though to AWS load balancer accepted format... that was the bulk of my earlier problem, especially handling the chain bundle. The AWS cert service, I assume, would eliminate the conversion problem for me. Thanks... I'll check it out
Buying SSL Cert through Bluehost (my domain registered, and blog hosted) and figuring out how to apply it my web-app, zejoop.com, hosted on AWS was far and away the most annoying and difficult chore in my development/deployment process as a relatively junior SW developer. If I could solve all inhouse within AWS (at reasonable cost) is be very happy. My cert just renewed, so until I roll change to AWS my https:// is down. If update is as difficult for me as original install was, then I guess it will be about 18 hours of aggravation. So I'll look into this, if the OP title is a reality.
I can't ssh into instance using the AWS documentation (I was pretty careful following the instructions and know I have the right instance id and region)--> "Permission denied (publickey)."
(I've since fixed this - I hadn't chmod'd right, and didn't account for working from an ubuntu machine)
I commend the spirit and attitude of your post as well, especially having also gotten a rejection. I am curious though, what exactly did you learn from this experience? I'd love to be able to claim the same, but given absolutely zero feedback from the process, I'm at a loss to do so.
- rejection postmarked 1:59 pm for zejoop.com
- one view of founder video
- zero views of demo video
- I am a single founder
- this was my third YC application, all for Winter sessions
Although there are many options available to accomplish casual event planning, that matters little if they lack the ability to solve a particular type of problem you may have. That's the situation I found myself in, struggling to improve coordination for gaming sessions among my friends. This post describes how I came to decide how to solve this problem for myself.
Yes. But imagine this on a scale of the big defense contractors. They won't 'eat themselves to death' as you put it but they are big enough (especially after major consolidations in the 90's) to sustain this behavior indefinitely.
Unfortunately a large part of their business model relies on fulfilling their commitment to seat engineers on programs as promised in the contract they signed with their customer, i.e., the USG. Filling seats is more important than achieving quality engineering outcomes. There are three big-time losers in that equation: [1] the taxpayer, [2] the "lifer" employee, and [3] the warfighter.