Good version to use in a production enviroment

18 views
Skip to first unread message

Ben Edwards

unread,
Aug 23, 2017, 11:55:37 AM8/23/17
to Ruby on Rails: Talk
Hi, we are setting up Ruby on Rails on a production server.  Advice on what version of ROR and Ruby to use would be great.  Obviuiously we want something stable and not too cutting edge.

Also advice on keeping it up to date, especially regarding secularity, would be great.  We have great Linux sys Ops in terms of general security, its the ROR bit of the stack I am asking about.

Regards,
Ben

Rolandas Barysas

unread,
Aug 23, 2017, 1:57:50 PM8/23/17
to rubyonra...@googlegroups.com
Hey,

I think it's safe to say that current newest stable releases (Ruby 2.4.1 and Rails 5.1.3) should work fine on production. Been running them for a while without any issues. Some production websites even run on Rails master (I think Basecamp is one of them).

In terms of future strategy, probably waiting a patch or two after minor/major releases is always a good idea. Read change logs, keep an eye on issue tracker and test updates on staging environment before updating production.

These are general guidelines that I use, but your milage may vary. Hope that helps.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/4facbb70-988b-4ab9-a50c-16bbaf762dd5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Rolandas

Ben Edwards

unread,
Aug 23, 2017, 5:23:39 PM8/23/17
to Ruby on Rails: Talk
Rolandas,

Thanks for that.  Have setup a master/prod and dev branch/database.  file structure is dev/eventtpuddle/ and prod/eventpuddle, with each having 'lib' etc in them.  Was thinking of putting a rails directory in each to keep everything in the git tree.  Does this make seance.  I guess I need to point Apache at a directory under rails but currently have been concentrating on writing ruby scripts to populate the database so not started using rails yet.  Just want to work out where stuff goes before I start.

I can use the dev for staging.

What is the easiest way of running two versions of ruby & rails, cant really go the VM route.

Ben

Hassan Schroeder

unread,
Aug 23, 2017, 8:07:01 PM8/23/17
to rubyonrails-talk
On Wed, Aug 23, 2017 at 2:23 PM, Ben Edwards <lo...@funkytwig.com> wrote:

> Thanks for that. Have setup a master/prod and dev branch/database. file
> structure is dev/eventtpuddle/ and prod/eventpuddle, with each having 'lib'
> etc in them. Was thinking of putting a rails directory in each to keep
> everything in the git tree. Does this make seance.

Not to me -- I'm really not sure what you're describing, but Rails has
a standard file layout; going against convention isn't recommended
if you're relatively new to Rails.

What exactly are you trying to do? Have you examined the default
generated layout? What is it about that you have problems with?

> What is the easiest way of running two versions of ruby & rails, cant really
> go the VM route.

I use `rvm` (Ruby Version Manager); some people use `rbenv`.

HTH,
--
Hassan Schroeder ------------------------ hassan.s...@gmail.com
twitter: @hassan
Consulting Availability : Silicon Valley or remote

Phil Edelbrock

unread,
Aug 23, 2017, 10:42:10 PM8/23/17
to rubyonra...@googlegroups.com
Latest stable is Rails 5.1.3 and Ruby 2.4.1. I'd not try to use older versions... upgrading deprecated stuff in Rails is a PITA, and older Rubys are slower and coming to EOL for security patches anyway. I'm also on Linux. Using Apache+Passenger+PostgreSQL to deploy. You can safely update minor releases as you go as they are released without a lot of pain. Start with current stable releases and move from there.

Good luck! Hope this helps.


Phil

Message has been deleted

Ben Edwards

unread,
Aug 24, 2017, 4:54:58 AM8/24/17
to Ruby on Rails: Talk

On Thursday, August 24, 2017 at 3:42:10 AM UTC+1, Phil wrote:

 Latest stable is Rails 5.1.3 and Ruby 2.4.1. I'd not try to use older versions... upgrading deprecated stuff in Rails is a PITA, and older Rubys are slower and coming to EOL for security patches anyway.  I'm also on Linux.  Using Apache+Passenger+PostgreSQL to deploy.  You can safely update minor releases as you go as they are released without a lot of pain.  Start with current stable releases and move from there. 

So Passenger works with RVM in Apache?

I think I am going with MariaDB (mysql).  Curious why you chose PostgreSQL? 
 
Good luck!  Hope this helps.

Yes a lot.
Ben



 

Phil

Reply all
Reply to author
Forward
0 new messages