3 ms·
> Rails made developers incredibly productive at building applications, but it was still painful and time-consuming to get them deployed. Developers might spend
by MBCook 4y ago
> Rails made developers incredibly productive at building applications, but it was still painful and time-consuming to get them deployed. Developers might spend weeks (or months) just on deployment.
I’ve never used Rails. What made it so hard to deploy? I always thought it was similar to PHP: setup a DB, maybe fill in a config file or two, and copy the code to the web server. was that not the case?
- my69thaccount 4y agoIt was common to use Phusion Passenger at the time and it had a similar deployment story.
- TheNewsIsHere 4y agoMy one engineer/admin/technical interaction with Ruby on Rails was as the person responsible for overseeing the design, and then the testing and deployment using Passenger on Apache, for a completely bespoke application at a nonprofit. It left an odd taste in my mouth overall, but it was a valuable learning experience and the application itself was neat. Getting it to run was sorcery.
- pvg 4y agoOne difference was that PHP was specifically designed to be launched by or embedded in a web server and Ruby wasn't. Getting that glue to an unfinicky, unclunky state took some time.
- danmur 4y agoLots of developers just weren't/aren't good at deploying things, I don't think Ruby was any more difficult personally.
- jdminhbg 4y agoThere was frequently more than just a DB; one thing Heroku made easier was adding things like mail serving, memcache, Redis, etc. The major issue in early Rails deployments though was the dependency hell you got pre-Bundler (equivalent to something like Yarn in the JS world). Most of the fighting with deploys I did was along the lines of "it works on my machine, why doesn't it work on the server?"
- _tom_ 4y agoOh, man. I remember that. It seemed like no matter how careful you were, your machines would not be the same, and you'd hit issues. We went to VMs to get things consistent.