I think the next step is to work on migration. I need to see if I have access to the current database so I can make some migration code.

I also need to modify the login code so that legacy passwords can be used once and then a new password will be forced. I think I'll let the same password be used since the point will be changing from a MD5 hash to a salted bcrypt hash.

Thank you so much for all of your hard work and effort on this, Gud!

I have access to the current database. I was trying to figure out how to upload stuff into the new database.

Might have to load the current data into a offline database and write some ruby code to suck in the old data and transform it into active record seed scripts.

Can't I just send you a whole bunch of SQL?

That will work just fine.

When you are ready with the SQL I can give you an private upload location on my private cloud if you want. Though just checking in on a branch would probably be fine. Once compressed they shouldn't be too huge.

Thank you so much for all of your hard work and effort on this, Gud!

Thanks! I hope people like the updated site once the transition happens. It should be much easier to read on mobile without breaking those who don't use javascript. Behind the scenes security holes will be fixed as well. Not that there there won't be work to be done afterwards as well.

Besides the single posts table, is there any significant difference between the two database schema I should be aware of?

The user table is pretty different mostly because of the way registration works. I'll need to do some custom work there anyhow to deal with using existing password hashes so that's not really a big deal. I think the bookmarks table carries a bit more data than the current one but that can be backfilled.

Just to note to other people reading this. Your passwords are not stored in the current database or the new database. So we're not passing around actual passwords at any point here, just hashes.