On New Server
Hi I'm Sean Reiser, this is my Personal Blog
My thoughts on the Game Stop situation:
When a hedge fund shorts 120% of a stock's float, gets caught with their pants down and is taken to the cleaners by people who use publicly available data learn about the situation they get what they deserve.
Pure capitalism will punish the greedy and that's what's happening here. Brokerage houses should not be halting trading on GME. The hedge funds shouldn't be bailed out. The biggest problem we've had is that when capitalism is going to drop the hammer on the greedy, we bail them out.
The people who are driving the price up aren't the problem, the funds who over shorted GME are.
I’m in the middle of a Drupal 8 -> Drupal 9 migration. After the data migration I decided to nose around the database and found a number of tables that I believe are vestigial and should’ve been dropped a while ago:
- Migration Tables - (migrate_map_upgrade_d7_*). tables that were used when I migrated this Drupal 7 into D8 5 years ago.
- Empty Field Tables (node__field_*) and Node Field Revision Tables (node_revision__field_*) that were from fields that were deleted years ago, generally from deleted content types. This also shows up for paragraph, taxonomy and media bundles.
The fact that this stuff lingers around surprised me. In my database management days, cruft always bothered me. Is there any danger in clearing this out by hand (dropping tables)? Do any developers monitor these things?
I know I'm in the minority, but I like the notion of the Touch Bad on a MacBook. It just should be in addition to the Function Keys instead of in place of them.
Over the last week or so I've made some progress towards upgrading this site:
- As I mentioned in a previous post I stood up a new server to look consider Vanilla Drupal 9.0 vs Lightning 9.0, vs Varbase. All three have their advantages but I have decided to stick with Varbase. A lot of the sites I build fit in Varbase’s wheelhouse. The 9.0 branch is far more modular than the 8.0 branch. Since I’ll be installing things with Composer on this site, this should work well for upgrading.
- I’ve given some thought to content types and built out new content types on for the new site. Here are the changes I’m making
- Converting all files (images, audio, docs) to media entities. Media in core wasn’t ready when I built this site now it is.
- Merge the Job Position, Portfolio and Case Study content types. There is a lot of overlapping data between these content types.
- The Notes content type is renamed to Post.
- For now I’ll have 2 landing page content types: One using paragraphs, which I’ll import the current page into, one using layout builder. I’ll migrate the current pages to layout builder after I launch so I can get rid of the dependance on Paragraphs by Drupal 10.
- First I’m working on migration scripts to get data into the system. I’ll setup JSON:API on a copy of this site to export content and use the Migration API. I expect 2 challenges:
- I’ve never had to create media entities from file fields. I’m sure there’s an example on the web someplace, if not I’ll have to do some hacking.
- I’m pretty sure I won’t be able to automate merging the content types I mentioned above. I look at this and figure it’s a half day to do it manually,
- This site that has little logic (a glue module and a module that extracts metadata for links). I’m pretty sure I build those with Drupal 9 in mind, but I’ll give them a once over.
- A combination of theming and site building. I’ll be moving to Bootstrap 4 in the process.
- Static site? I keep looking at Tome. With small changes this should be possible for my site (mostly I need to rethink my use of webforms.
You know how they say that in best relationships you're always learning something new about your partner? I know I mentioned that Anne and I have been watching the rebooted BSG. We got to the end of Season 3 tonight. And I learned that Anne does not know the lyrics to All Along The Watchtower.
In a Facebook covid survivors group someone posted "I heard someone died from the vaccine". Here was my response:
I don't know if someone did but I'm sure someone will die from the vaccine, probably through an allergic reaction. The math says the the risk of dying from the disease is MUCH HIGHER than dying from the vaccine. We've all had this disease, many of us are long haulers dealing the the effects months later. As I'm sitting here 10 months later sill having issues climbing the stairs, I don't know what the long them effects of this disease are on me.
It's risk assessment. On average 10 people die from taking low dose aspirin a day, but it saves more lives for folks with cardiac issues. 100 people will die in car accidents today, but we have decided that the benefits of faster travel outweigh the risk. Nothing is perfectly safe. Everything has risk. The question is, "Do the benefits outweigh the risks".
Disclaimer : I'm a Computer Programmer so you should speak to your Doctor to see if you have additional risks before taking it, especially if you have problems with vaccines, medicines or have other medical conditions.
I am as upset now watching these rioters storm the capitol as I was at the rioters who took advantage of the BLM protests.
I spent my "free time" the last few days standing up a new sever on linode. It's been a year or so since I've run a built my own server. I have some potential projects popping up where I felt it was a good idea to flex that muscle again.
My current site is based on the Varbase distribution and I like the time it saves me from a development standpoint, but there are costs from a performance standpoint you take a hit. I want to really take a day or 2 to look at Varbase vs Lightning vs Vanilla Drupal 9. The reason I wanted on its own sever is to better evaluate perforce issues.
Time for the annual updating of copyright notices. Before anyone asks, doing it in code may make it unenforceable.