After many years, I decided that my gem nondestructive migrations needed a facelift. It had some cruft I didn’t want, was packaged in the wrong way, and Alex Chaffee brought up a legitimate objection to the nuance of its name: the discriminating factor that differentiates these migrations is not destruction, he argued, and so the gem is likewise misnamed.
For all of these reasons, and to fix a problem with bundler’s ability to smoothly upgrade, I am renaming and replacing nondestructive migrations with nonschema migrations.
As well, this approach implements different versions of this gem for each different version of Rails, which became necessary when
was renamed to
where X.X is the Rails version number. This strategy will allow bundler to easily pick up the new version of this gem when you upgrade Rails, and in the future I will release this along with Rails’ own release schedule.
it is still possible to host your sitemap on external S3 buckets. You must set up a subdomain of your domain pointed as an Alternative Domain Name for your CloudFront distribution, and in order to do this you must go through domain verification with AWS.
Tested codebases are the most signficiant development from Rails and Agile over the last 15 years. End-to-end testing, in particular, is the defining reason why Agile and Rails have been so successful. Not writing tests should be seen as akin to malpractice in software development. Hiring someone to write untested code should be outlawed.
Confusingly, bundler can have more than one version of Rails installed at once. In this short post, I will review how to check which version of Rails bundler has installed, and how to know which version of Rails you are using to make a new Rails app.