Quote:
Never play on a patch day.
Issue is, when you're the one doing the patch..
LOL.
Yesterday was a migration test disaster.
First of all, the Discourse team seems to attempt to bully me to do an impossible upgrade from
vB3 to
vB4, an upgrade which does not exist and is not available. LOL.
Then, when I explained that to them, they shut me down, shut down a bug report, and decided to ignore us completely.
It was a very strange day, for sure.
Then, working on trying to fine tune the migration by making manual search and replace changes to the test migration postgres database, raking the db (which means basically cooking a million plus posts from raw format to final format) the postgres db crashed.
The worse part was each search and replace in a docker discourse app took 30 minutes to an hour, and I had to do at around 10 of these search and replace db operations, so that took the whole and and then, afterward, to have the entire discourse rake process crash, well..... it was a very bad day all around.
However, I think I will start from scratch, ground zero today, with test migration 2.
However, this time I will do more intensive modifications to the
vbulletin.rb migration script (my original plan) versus manually doing search and replaces in the discourse database (suggested by someone, so I thought I would try it), and start from scratch.
In addition, I will not post any bug reports on the meta discourse site or interact with any "migration experts", as that has not worked out either (trying to be sociable and "collaborative" has not yielded any fruit at all) and just leads to unnecessary social conflicts with "discourse experts", which are totally distracting from the task and have been, at best, unproductive.