I was under the impression that the good folks at github were using Vagrant in some capacity. Assuming they've used it or heard of it I'm wondering if/how it fell short for their server based projects.
Regarding the part where you say "document everything". I'm assuming you come from a mid-sized company standpoint where there is more than 1 person working on the app. I might be wrong but I think documenting everything from the start is counterproductive.
Any examples of library-in-app in the wild. I get the idea, but want to know what this looks like in practice.<p>Mounting engines or Sinatra apps? Creating a new gem to for extractable functionality? Just curious about what this looks like under the hood.
I don't agree with code is not readable. If the code is not readable, you really need to look at your naming conventions and abstractions.<p>Using documentation as an alternative to readable code is a pitfall.
Could you give more detail about how you use inner-app services? They seem like a good way to manage project complexity, but I can't find much documentation on how they work in Rails.