update – Fox’s Projects

[Solved] MySQL docker on Unraid does an unwanted upgrade

the logo of mysql, showing the name and the outline of a dolphin.

I usually do not fear updates, but when it comes to databases, I am getting really careful with updating them. It wouldn’t be the first time when a database goes plonk after this.

So what happened? My MySQL docker got updated becuase I simply misclicked and of course, the thing broke. The update script, which was set to “latest”, performed an upgrade to 9.x instead of sticking to the latest 8.x version.

After some research, I read that one can enter “mysql:8.2.0” in the repository field. After entering this and starting the docker, the software got reinstalled with the proper version and everything worked again. I must’ve been lucky that the database itself was not migrated to v9 already, I guess.

[MASTODON 4.2.10] How to update Mastodon to a new version

Updated on 26-08-2024. For the old version, click here.

Contents:
1. UPDATE
2. RUBY VERSION ISSUES
3. RUBY GEM ISSUES
4. CHARLOC_HOLMES GEM ISSUES

So a new release came out and it is important to get this update as soon as possible! This manual is a transcript of the way that I have updated my Mastodon instance. Please make sure you make proper backups and use your brain while updating things.

A guide to making a Mastodon backup can be found here.

Linux flavour: Debian
Update from: 4.2.xx

Log into your server
```
su - mastodon
```
```
cd /home/mastodon/live
```
```
git fetch --tags
```
git checkout [type the most recent version here, starting with the letter v. For example; v4.2.5
```
git checkout v4.2.10
```
If you get a ruby version error, please see bottom of this article for a fix! bundle install
```
yarn install
```

RAILS_ENV=production bundle exec rails db:migrate

#NOTE: You might get a ruby error which then suggests you to enter the command "bundle install". Do that and then run the RAILS command again.

RAILS_ENV=production bundle exec rails assets:precompile

```
exit
```

OPTIONAL:
After updating, you might get a notification to update the browserlist database. You can do that with the following command:

npx update-browserslist-db@latest

Okay, you can now choose to either reboot or restart the services.

REBOOT:

This command may vary, depending on your Linux flavour.
```
systemctl reboot
```

RESTART:

This command may vary, depending on your Linux flavour.

systemctl restart mastodon-sidekiq
systemctl reload mastodon-web

Optional:

systemctl restart mastodon-streaming

RUBY VERSION ISSUES

My system was unable to find the required v3.2.3 of Ruby and I have fixed this by doing the following steps:

Please make sure that your path is correct.
```
git -C ~/.rbenv/plugins/ruby-build pull
```
```
rbenv install 3.2.3
```
*WAIT TILL DONE* (it may take a little while)
To check all the installed versions type:
```
rbenv versions
```
To set v3.2.3 as the global version, type:
```
rbenv global 3.2.3
```
To double-check the active, installed version, type:
```
rbenv versions
```
Done!

This manual is a transcript of the way that I have updated my Mastodon instance. Please make sure you make proper backups and use your brain while updating things.

Sources: https://richstone.io/where-is-ruby-3-0-0-on-rbenv/

RUBY GEM ISSUES

After entering…

RAILS_ENV=production bundle exec rails db:migrate

…you might get a ruby gem error like:

Could not find rexml-3.3.5, strscan-3.1.0 in locally installed gems
Run `bundle install` to install missing gems.

Enter the command “bundle install” and after that run the RAILS command again.

CHARLOCK_HOLMES ISSUES

The charlock_holmes gem may fail to build on some systems with recent versions of gcc. If you run into such an issue, try

BUNDLE_BUILD__CHARLOCK_HOLMES="--with-cxxflags=-std=c++17" bundle install.

How to fix Docker update “not available” in unRAID 6.8.3

Because something went wrong probably and it takes unRAID literally ages to issue an update. So here’s the fix!

(until you restart the server)

SSH into unRAID and edit this file: /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php

replace this line:

preg_match('@Docker-Content-Digest:\s*(.*)@', $reply, $matches);

with this

preg_match('@Docker-Content-Digest:\s*(.*)@i', $reply, $matches);

Sauce: https://www.reddit.com/r/unRAID/comments/nk1sa2/how_to_fix_docker_update_not_available_in_unraid/

Upgrading the firmware of the Zyxel VMG8324-B10A

WARNING. As explained on the “About” page that this is a blog based on my notes, whether they fail or not. So proceed at your own risk.

My Zyxel router currently has firmware version 1.00(AAKL.14)C0 and since Zyxel is a good boye, they keep their devices up to date. Like all manufacturers should do IMO.

Aquire all the firmware files that are available by going to ftp://ftp.zyxel.com/VMG8324-B10A/
Remove the files that are older than your current firmware, in my case v.14
BACK UP YOUR CURRENT FIRWARE AND SETTINGS
Apply ALL updates one by one. Do not skip versions.

Good luck.

In-place upgrade of a Themelr template (Joomla)

How to Fix the error after updating to Joomla 3.9

If you updated to the latest version and the following error appears when you try to launch Themler please follow the instruction below:

Fatal error: require_once(): Failed opening required '[...]/administrator/includes/toolbar.php' (include_path='.:/usr/lib/php7.2') in [...]/templates/[theme_name]/app/index.php on line 25

Open theme folder on the server: www/Joomla_directory/templates;
open /app folder;
open index.php for editing in any html or text editor;
find the line
require_once JPATH_BASE . DS . 'includes' . DS . 'toolbar.php';
and replace it with the following line:
$prefix = version_compare(JVERSION, '3.9', '>=') ? 'sub' : ''; require_once JPATH_BASE . DS . 'includes' . DS . $prefix . 'toolbar.php';;
open /app/start folder;
open data.php file for editing and follow step 4;
open manifest.php file for editing and follow step 4;
start Themler.

Fake JBL Xtreme update

I am trying to connect the official app to it and it cannot detect the speaker. Assuming that the software is written correctly, I think that the inside of this speaker differs from the original. Oh well!