The asset pipeline is great and confusing at the same time. It performs differently in development than it does in production, and as such you can’t be really sure everything is going to work once you deploy it, unless you really understand it, of course.
One of my gripes (or possibly misunderstandings) with Rails is that you have to make the schema within Rails. I find that difficult – I want to plan it externally, create the schema, and then use it in my app. Perhaps there is an easier way to accomplish that, but here’s what I do.
OK, before you go yell at me, I know enabling detailed error messages on a production web application is a Bad Thing™. The security guy in me hates finding a production application that spews back all kinds of details to a user when something goes wrong, and I’ve had many a developer disable detailed error messages on their production applications.
Like PHP or any other web programming language, you can deploy multiple instances of the same Rails application on the same server. One reason for having multiple instances on the same server would be the need for multiple exclusive data sets while saving costs on hardware and administration from having to maintain multiple boxes. All you need to do is duplicate the application files, change your database configuration in each directory, and configuring some virtualhost settings.