I'm getting better at this the second time around, for sure; but I'm not an expert on ruby for sure.

I harbor no ill will that the leadership team at meta gave me the cold shoulder regarding vB3. I don't blame them. vB3 was EOL a very long time ago.

In addition, the leadership team over there are very smart tech development guys, and most tech dev guys in that league are not very "customer service support touchie-feelie".

I can vouch for that. When I am developing some difficult code, and someone is starting to 'annoy' or 'distract' me; and I also get very edgy. I think this is the nature of tech and developers.

In addition, those leadership guys over at discourse meta are funded by at least two venture capitalists. This creates enormous commercial and financial pressure in startups, so I cannot blame them for choosing a different road than me.

For example, I don't need to get "filthy rich" and am more of a "Zen, live by the beach, guy these days", and so I made the personal choice to never join a tech startup; and now I'm retired and living on the seacoast with the sound of the surf in my ears 24 hours a day and the warm ocean breeze all the time. That was my choice. I don't fault others for choosing the stressful life of venture capital funded startups. Plus, most people work at stressful jobs with the goal of living in some great location, like next to the warm ocean or in a mountain cabin. I have already reached that goal 10 years ago. I would be wrong of me to fault others for trying to reach the same goal and living in a stressful situation, right?

To each his or her own. We all follow our own path and move our feet to the sound of a different drummer.

Also, I greatly appreciate that discourse open sourced their core software and that the created a vb4 migration script which I can modify for vb3.

So, I am perfectly OK to share with discourse any lessons learned from this migration (if I actually get it done),

And, I will not post any more bug reports over there regarding this migration or ask any questions.


Because the discourse install for non-docker is a nightmare and that opens up a very big can of huge worms.

Migrations like this can sometimes take months of planning and weeks of tests and execution. It's slow going, but lets' see....... I have already started "round two" today:


VBulletin 3.8 to Discourse on Docker Migration Test Take Two