DMPRoadmap / roadmap

DCC/UC3 collaboration for a data management planning tool
MIT License
103 stars 110 forks source link

Run the initial upgrade of the codebase #2449

Closed briri closed 4 years ago

briri commented 4 years ago
mariapraetzellis commented 4 years ago

Estimating 3+ days of work.

briri commented 4 years ago

Work will be done in the rails5 branch which will be kept up to date with the changes made to the development branch for our remaining tickets this sprint.

briri commented 4 years ago

Here's a list of the things done to get from 4.2 to 5.0

briri commented 4 years ago

Here are a list of tasks done to get from 5.0 to 5.2 (including the step to 5.1):

NOTE Cookie serialization has changed in Rails 5.2. This will cause issues for uses that have cookies that have not expired when then go to the newly upgrade site. We should be able to deal with this through messaging to the user community.

briri commented 4 years ago

Next steps:

Ensure all tests are running. It looks like we will need to add optional: true to many of the belongs_to rellationships

briri commented 4 years ago

Ran through and got all but 2 tests passing. Needed to make the following adjustments:

briri commented 4 years ago

NOTE: that the way Rails handles app credentials has changed in 5.2. There is no longer a config/secrets.yml file. It has been replaced by a config/credentials.yml.enc file and a config/master.key file.

Everyone should read this blog post: https://medium.com/cedarcode/rails-5-2-credentials-9b3324851336

We can check in the defaultcredentials.yml.enc generated for this open source project. We will need to update all of our individual deployment strategies to use our own copies of both files.

To generate these files in your own instances, you will need to run EDITOR=vim rails credentials:edit (swap in your favorite editor)