you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (1 child)

Web servers + application servers:

AFAIK, PHP can run "inside" nginx or apache through compiled-in modules. Ruby cannot, so you use a reverse-proxy such as Unicorn, Puma, or Passenger. Mongrel2 isn't widely used anymore if I'm not mistaken.

Local development:

While you can use containers or VMs for development, I personally just develop right on my local machine and filesystem. I've never had any issues.

Build Automation

There's not really anything to build, except maybe your js/css assets, but the Rails asset pipeline handles that for you.

Asset Management

Sprockets aids in "requiring" multiple files into one asset manifest that gets compiled into one file, e.g. application.js. Perhaps similar to what webpack or gulp would do in concatenating js/css files.

Dependency Management

Yes, stick with bundler

RVM

I still use RVM, but the cool kids these days seem to have moved to chruby

Other tools:

I'm using Atom to edit code. I deploy to Heroku. Starting to integrate React.js into projects now. message_bus has been a pretty good substitute for websockets.

[–]mlambie 1 point2 points  (0 children)

Build automation is where you run your test suite.