Well, I wanted to drop Coherence in one of the developments I’ve in production but it was hard to evolve that from Phoenix 1.4 to Phoenix 1.5, I can see there’s a topic from 2018:

I wasn’t aware of this, I did (like many others) modifications in my fork of coherence to adapt it to Phoenix 1.5, you can see it here:

So, as I said, days ago I had two options:

1. Drop the whole development of Dymmer and start it from scratch, because it’s awful, it cannot get worse if I start it from scratch, right?
2. Migrate step by step, dependency to dependency, and part at a time.

I’m not sure about your experiences, but mine are that migrations “all at once” don’t work. You can get a really good brand-new web app doing what you desire, but the old one is working and generating a bit of money, so do you want to jeopardize it?

So, I started migrating to Phoenix 1.7 and the first stop was phoenix_markdown, that library wasn’t updated for longer and the earmark changed a bit, you can see here the changes I made:

https://github.com/dymmer-code/phoenix_markdown

Second stop, recaptcha, looks like none was using that for longer, isn’t it? There’s another called HCaptcha that looks like the new kid on the block, well, finally, I made these changes:

https://github.com/dymmer-code/recaptcha

And last stop, at the moment, Coherence. Phoenix 1.7 has a new-brand way for auth and even getting solutions like Pow, Coherence was a thing some time ago, but it was abandoned. As I introduced, I made changes for Phoenix 1.5 helped by others who did the same, but looks like most of the people left Coherence and it hasn’t been supported for Phoenix 1.7… until now:

I did this branch for Phoenix 1.7 BUT not using LiveView at the moment, so don’t get too excited, it’s only a way to give me enough time to perform the next steps of the migration for the project.

Maybe I write a bit more about migrations in a future, I’ll let you know