Ruby on Rails runs on a vps fragment

Question

What are the main mistakes and tricks when running Rails on a small fragment (256 MB)? What is the best server setup for cramped spaces? Passenger, Nginx, Mongrel? What is the best background task processor in this environment? Why do you need to follow? I would like to hear the stories of the people who did this and ran into some virtual walls.

Answer 1

I run Passenger on 256mb slicehost, no problem. Much simpler, much easier to configure than any other alternative. For background I use Starling and Workling, and Ryan Bates has an excellent screencast on how to use both together.

Answer 2

Nginx proxying for multiple mongrels. Updating gems can cause you to run out of memory, but this can be resolved by downloading and compiling rubygems from the source. You will not have problems using cron for background tasks, as it is very light.

Answer 3

256- nginx . , , , monit, .

Answer 4

I offer the passenger simplicity and a small area. I have this on my VPS with multiple domains (256MB VPS on RailsPlayground) and there are no problems yet. In addition, the Starling / Workling combination works very well, or you can even use the spawn plugin if your site is not huge (it’s dead simply).