4 ms·
This is a nice useful blog post, but it does lead me to question to state of Rails -- is it me, or is it incredibly complicated these days to build a production
by davedx 15y ago
This is a nice useful blog post, but it does lead me to question to state of Rails -- is it me, or is it incredibly complicated these days to build a production ready Rails site?
I still love the simplicity of developing with Rails, but all these things you need to remember to deploy give me cold sweats.
- cmelbye 15y agoNo, this is not necessary to build a production-ready Rails site. If you want to send your files through a CDN, then you'll need to perform this configuration (which is still easier than writing the logic yourself.)
- danneu 15y agoDeploying is easy. Using a CDN, sprites, and other details in this blog post are iterative optimizations, not deployment prerequisites. They certainly aren't more trivial to implement if you aren't using Rails.
- inkel 15y agoI agree with you. I'm not doing Rails anymore, I'm working with Cuba + gs + dep + Ohm + mote, and I find it easier and less bloated than what Rails has become. Rails 3.x, though with a couple of good ideas, it's not as easy as it used to be to start developing an app, less say deploying it. Too many helpers and technologies to learn, IMO completely unnecessary.
- SkyMarshal 14y ago>Cuba + gs + dep + Ohm + mote I thought I'd heard of everything, but I haven't heard of a single one of these. Any chance you can write up a blog post about building websites with them and post it?
- matlock 15y agoRails provides great performance and when coupled with Apache/Nginx delivering Assets is not that big of a deal. But as Heroku doesn't provide any proxying it is upon every developer to implement something like this. Though doing it takes probably less than an hour, so compared to earlier times it is incredibly easy. And someone else already mentioned that this is not something you would do from day one. The first deployment (especially with Heroku) is incredibly easy, but there is a lot to build upon once you have that application up and running.
- mrinterweb 14y agoNone of these features are necessary to build a production-ready Rails site. Before Rails 3, people built and deployed production-ready Rails sites. Production asset optimization was left up to the developers to figure out. Rails 3 makes asset optimization very easy by comparison to what needed to be done before. Rails has not become more complicated to develop for. Rails 3 just has more features than it used to have. If you want to use more features, the features are there for you. If not, you can ignore them.
- tferris 14y ago> is it incredibly complicated? Yes it is and frustrating is that you have to read spec over spec to follow all the conventions. You can be very fast with Rails and all its gems but to get there takes time and it's no fun anymore.