On Thu, Jul 18, 2019 at 1:05 PM David McDonald wrote:
> I think I just need to backup my nginx.conf, and sites-enabled folder.
If you put all your config files into a git repo it'll make it easier to see
what's getting changed by the upgrade process.
It's all useful if you wind up going the
My apologies but I have already reverted back to the snapshot. It seemed
that my setup in /sites-enabled/ was only setup with a default file that
wasn't my original file after the upgrade. The reference to my ruby path
was also incorrect. And I had to modify some permissions to log folders
On Thu, 18 Jul 2019 at 19:15, David McDonald 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
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
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
*Hello Partner’s*
*Please share to me your best consultant’s for the above role with our
client.*
*Only USC/GC independent Profiles.*
We’re looking for an experienced engineering leader who wants to
contribute to our growing company. This is a rare opportunity to join a
successful
6 matches
Mail list logo
