Thursday, July 18, 2019
If it were me, the leap from 14 to 16 to 18 would be too much to worry about so instead of upgrading a snapshot, I would just create the new server with 18 and then work on getting the app to run on it. Once it seemed to be running correctly redirect traffic to it.
Your approach should also work by keeping things very incremental - when you note that a configuration file seems to be missing refer back to the original server's version and keep the new one as close to parity with the original as possible. There is too much information about updating and maintain legacy Rails apps out there to really make a specific recommendation for how to guides but the best place to start is simply reading the official Rails guides on updating/upgrading to see what you're in for and that using that to google-fu for how-to articles that mirror your own situation.
Once you've got things running on a newer Ubuntu version come up with a plan for regular update maintenance because it's much easier to update incrementally on a consistent basis than it is to just let a legacy app sit and accumulate huge amounts of technical debt. Good luck!
Your approach should also work by keeping things very incremental - when you note that a configuration file seems to be missing refer back to the original server's version and keep the new one as close to parity with the original as possible. There is too much information about updating and maintain legacy Rails apps out there to really make a specific recommendation for how to guides but the best place to start is simply reading the official Rails guides on updating/upgrading to see what you're in for and that using that to google-fu for how-to articles that mirror your own situation.
Once you've got things running on a newer Ubuntu version come up with a plan for regular update maintenance because it's much easier to update incrementally on a consistent basis than it is to just let a legacy app sit and accumulate huge amounts of technical debt. Good luck!
On Thu, Jul 18, 2019 at 1:15 PM David McDonald <daveomcd@gmail.com> wrote:
I have an ubuntu-server running version: Ubuntu 14.04.5 LTS. I want to upgrade it to Ubuntu 18.04 LTS. I snapshotted my server and tried to upgrade it to 16.04, and then 18.04 but ran into some issues where it seems through the upgrades I lost some of my configuration files. When prompted by Ubuntu through the upgrades I chose to keep the local versions but I guess it didn't ask about those configuration files. My question is what is a recommended approach to upgrading? I currently use passenger, nginx - are there any guides that discuss how to do this with that setup? Or am I better off creating a new server, setting it up and then redirecting to it? Another important note is this server/web application is for small internal usage. probably dealing with less than 30 users on a daily basis... I appreciate any guidance! Thanks!--
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/68ff7e77-8957-4185-aa99-40ae261ed0d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Brandon McClelland
User Support Technician
Steve Jackson Games
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/CADuEqH%2B7Fts2nPoi7fb1t5933vmVZGF1uWZAEhPJ%2BjuKgF-gNw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment