neonlex

Which part of what?

I don’t understand your answer, that’s basically what wmf described. Put a proxy or load balancer in front of your service.

I don't like the idea of not having my development certificates under control. They should be as secure as the production certs in my opinion. I use PHPKi for that purpose, it's not pretty but easy to setup and it runs in my own environment.

I used this font since more than a year. It's great but a week ago I started using Source Code Pro.

Thanks!

How can I remove a project?

Have a look at AWS OpsWorks.

I also strongly disagree. The real problem is that browsers can't use them as good as they should. If you take for example a RESTful API, the verbs make totally sense and especially one of the mentioned verbs. PATCH is a great verbs if you use it like it was specified. I personally like the idea of giving more freedom to chose the verbs. Imagine you could use for a Twitter API something like: FOLLOW /users/123

second

ssl is handled on app basis not in the load balancer and by the way, you can hook into everything by rewriting or overwriting the recipes

OpsWorks gives you better features, try out to start a small stack and then also have a look at the default cookbooks, there you can see what you can do with OpsWorks: https://github.com/aws/opsworks-cookbooks

But OpsWorks is the answer for the problem.

it's easy, but also a bit hacky... because opsworks triggers multiple lifecyle events and also distributes the chef config if you solve the config problem, maybe with a static example you're pretty much done

let's see how the service grows

you get a much better orchestration as you could with chef server you also have much faster interactions, better life cycles and to the searching... you get every information of evert machine under your fleet it is much much more better the chef server