Multitool.org- Into the Fediverse!
-
I suspect that there is allways someone who doesnt like changes and those who dont like much current platform. I just hope plans goes well without big hiccups.
-

-
This needs to happen to keep this place up and running

-
Bringing this one back because I have been working on the plans again lately and I think it's a good time to start sharing where we are at. Here is the migration plan I have developed so far, translated into English by our friendly neighborhood AI, and subject to change as necessary:
Goal: Move all Multitool.org properties to a new, modern, Fediverse‑capable hosting environment wit\h minimal downtime, maximum safety, and a clean, staged rollout.
1. Hosting Providers We Selected
You were choosing between Hetzner and Elestio. We ended up with a hybrid recommendation:Primary Hosting (Main Sites, High Performance):
Hetzner (Germany/Finland)
Best price/performance ratio in Europe-Excellent for WordPress, MediaWiki, PrestaShop, NodeBB
-Bare metal or cloud instances
-Very stable, very fast, very inexpensiveFediverse + Managed Services:
Elestio (Luxembourg)
Fully managed deployments-Excellent for PixelFed, NodeBB, Mastodon, Lemmy, etc.
-Hardened security, automatic updates, backups
-Tailor‑made for the kind of Fediverse‑native stack you’re buildingYour final leaning:
You were strongly leaning toward Elestio for the Fediverse components and possibly for the forum, because of the managed security and the fact that they specialize in exactly this kind of setup.2. Old → New Software Stack
Here’s the exact mapping we discussed:Current Site Old Software New Software
Multitool.org (main site) Joomla WordPress
Forum.Multitool.org SMF NodeBB
SAKWiki.com TikiWiki MediaWiki
MTO Gallery Custom / legacy PixelFed
EDC‑TV WordPress (stays WP) WordPress (migrated)You also mentioned possibly making everything Fediverse‑compliant, but we agreed:
-PixelFed is perfect for the gallery
-NodeBB has ActivityPub support
-MediaWiki has partial ActivityPub support (but not perfect)
-WordPress can be ActivityPub‑enabled via pluginSo the plan is Fediverse‑enhanced, not Fediverse‑exclusive.
3. Build Order (Development Order)
You clarified this yourself — and it was the right call:Build the Forum FIRST (NodeBB)
-Most complex
-Needs the longest testing period
-Your moderators need 3 months to learn, tweak, and debugThis becomes the “model” for the rest of the migration
Build PixelFed
-Easy to deploy
-Lets you start populating media early
-Helps unify branding and social presenceBuild the new Multitool.org (WordPress)
-Low‑interaction site → low‑risk migration
-Good candidate for early content import testingBuild EDC‑TV (WordPress)
-Straightforward
-Lets you test video embeds, podcast feeds, etc.Build SAKWiki (MediaWiki)
-Large content import
-Needs careful template/module migration
-Should be done after the team has experience from earlier migrations4. Release Order (Public Rollout Order)
This is different from the build order — exactly as you said.Multitool.org (main site)
Low interaction → safest to cut over first.EDC‑TV
Also low‑risk, mostly content‑driven.PixelFed
Once the main sites are stable, you introduce the Fediverse component.SAKWiki
High‑traffic, high‑importance, but stable once migrated.Forum (NodeBB)
The final and most sensitive migration.
By this point, moderators have had 3 months of training and testing.5. Migration Method
This was the backbone of your plan:
Run the new server in parallel with the old one
No downtime, no surprises.
Build everything on the new server first
Nothing touches the live sites until fully tested.
Import content one site at a time
Starting with low‑interaction sites.
Shadow Production Phase
Before each cutover:-DNS still points to old site
-New site runs in parallel
-You and your team test everything
-Only when approved → switch DNS
Full rollback plan
Because the old server stays online until the entire migration is complete.6. Estimated Timeline
You said: “All going well, this should take less than three months.”Here’s the breakdown we built:
Month 1
-Deploy servers (Hetzner + Elestio)
-Build NodeBB forum
-Begin moderator training
-Begin PixelFed deploymentMonth 2
-Build Multitool.org (WordPress)
-Build EDC‑TV (WordPress)
-Begin content imports
-Continue forum testingMonth 3
-Build SAKWiki and Multitool Encyclopedia (MediaWiki)
-Finalize PixelFed
-Build new MTO Store (WooCommerce)
-Finalize all content imports
-Begin staged DNS cutovers
-Forum goes last after full moderator approval7. Why This Plan Works
Because it’s:-Incremental
-Low‑risk
-Fully reversible
-Compatible with your workflow
-Designed for your cohosts’ technical comfort level
-Optimized for Fediverse integration
-Built around your real traffic patternsIt’s the right plan for the size and complexity of your ecosystem.
I've selected NodeBB as the replacement for SMF as it will provide the closest to our current configuration as change = BAD. If we can keep the interface as close as possible, it should minimize user complaints, although with the errors and downtime we have been experiencing lately I think members will be glad to see something done about it, and recognize that we have had 20 years out of SMF and that's pretty damned good IMHO.
Def
-
Oh, and I expect to do much of the heavy lifting behind the scenes since its a fresh build, only calling on Micah when I need to or when there's serious stuff to do. He's busy with work and since it's a fresh, clean install on a new server, and I have various AI's to back me up I should be able to handle much of the build myself.
When it comes to content migration, I'll probably leave that to Micah because we don't want me to smurf up 20 years of content.
We will also be changing software for some sites, either because of convenience, updating or that it's just a good idea.
The main site at MTO is currently running on Joomla, and that will be migrated to Wordpress.
The Wikis will go to MediaWiki, which (I believe) is what Wikipedia is running on, so it will be supported better/longer than TikiWiki.
The MTO Gallery, which is running on Gallery 3 hasn't been supported in many years and was barely useable when we created it, and we will replace it with PixelFed, which we experimented with last year. This not only allows us to have a photo hosting website like Photobucket or Imagur that can be linked to on the forum, but also it provides an IG like platform capable of operating independently.
The MTO Store is currently running on Prestashop, which wasn't cheap and has been largely dysfunctional the entire time we have had it. WooCommerce is free, open source (like most of what we use here) and integrates better with WordPress, so it makes more sense to change over.
As mentioned, the forum goes to NodeBB, not because it's the best but because it resembles SMF the closest... and it's pretty damned good. As per the AI:
NodeBB is honestly one of the smartest moves you can make for Multitool.org — especially given the size of your community, your moderators, and the long‑term Fediverse‑enhanced ecosystem you’re building. Since you’re seriously considering it as the SMF replacement, here’s the deep‑dive you actually need: what NodeBB is, why it’s so different from SMF/PhpBB-era forums, what it excels at, and what to expect when you run it on your new servers.
I’ll keep this tailored to your use case, not generic marketing fluff.
What NodeBB Actually Is
NodeBB is a modern, real‑time, JavaScript‑based forum platform built on:
- Node.js (server)
- MongoDB or Redis (database)
- WebSockets (live updates, no page reloads)
- A modular plugin/theme system
- A fully responsive, mobile‑first UI
It’s not a “forum script” like SMF — it’s a web application.
This is why it feels fast, smooth, and modern compared to the old PHP forum engines.
Why NodeBB Is a Massive Upgrade from SMF
Here’s the stuff that matters to you and your community:
1. Real‑time everything
- Replies appear instantly
- Notifications are live
- Typing indicators
- No page refreshes
It feels like Discord + a forum had a baby.
2. Mobile experience is actually good
SMF on mobile is… well, SMF on mobile.
NodeBB is:
- Touch‑friendly
- Fast
- Clean
- No zooming
- No broken layouts
Your users will feel like the forum finally entered the 2020s.
3. Plugin ecosystem is strong
You get:
- Polls
- Reactions
- Chat
- Awards
- Uploads
- Social login
- SSO
- ActivityPub (Fediverse integration)
- SEO tools
- Spam protection
- Analytics
And unlike SMF, plugins don’t break your forum every update.
4. Themes are modern and customizable
Persona (default)
Harmony (newer, cleaner)
Plus dozens of community themes.You can also fully customize CSS without hacking core files.
5. Performance is insane
NodeBB is lightweight and fast even on modest hardware.
On Hetzner:
- A CX32 or CPX31 instance will handle your entire community easily
- Redis is extremely fast for real‑time workloads
- Caching is built‑in
Your forum will feel instant.
6. Moderator tools are excellent
Your mod team will love:
- Live flagging
- Real‑time chat with users
- Post queues
- IP tools
- User notes
- Category‑level permissions
- Bulk moderation
And because it’s modern, it’s intuitive — no more SMF‑style “where the hell is that setting?”
7. ActivityPub support
This is huge for your ecosystem.
NodeBB can:
- Publish posts to the Fediverse
- Receive replies from Mastodon/Pleroma/etc.
- Let users follow categories or threads from their Fediverse accounts
This fits perfectly with your PixelFed + WordPress ActivityPub + MediaWiki plan.
What Running NodeBB Is Like (Admin Experience)
The Admin Panel
Clean, modern, and organized.
Everything is in:- General
- Users
- Plugins
- Themes
- Appearance
- Settings
- Advanced
No more digging through 20 pages of SMF settings.
Updates
- One command updates the whole forum
- Plugins update cleanly
- No template conflicts
- No “white screen of death”
It’s the opposite of SMF’s fragile mod system.
Backups
Because it uses Redis or MongoDB:
- Backups are fast
- Restores are easy
- No 500MB SQL dumps
Elestio even automates this if you host there.
What You Need to Run It
Server Requirements
- Node.js
- Redis or MongoDB
- Nginx reverse proxy
- Let’s Encrypt SSL
On Hetzner, this is trivial.
On Elestio, it’s one‑click.
Your Expected Cost
If hosted on Hetzner:
- €18–€26 CAD/month for a CPX31
- Redis included
- Plenty of power for your traffic
If hosted on Elestio:
- $45–$70 CAD/month
- Fully managed
- Automatic updates
- Automatic backups
- Hardened security
You were leaning toward Elestio for the forum because of the security and maintenance benefits.
Migration from SMF
NodeBB has an official SMF importer.
It brings over:
- Users
- Passwords (converted)
- Categories
- Boards
- Topics
- Posts
- Attachments (optional)
You will need:
- A staging server
- A test import
- Moderator training (you planned 3 months)
- A final import before cutover
This fits perfectly into your migration timeline.
What Your Community Will Notice
Instant improvements
- Faster
- Cleaner
- Easier to use
- Better mobile
- Better notifications
- Better search
- Better moderation
- Better media handling
What They Might Resist
- The UI is different
- Some old SMF workflows disappear
- Some users will miss the “classic forum look”
But after a week, most people prefer NodeBB.
Bottom Line
NodeBB is:
- Modern
- Fast
- Real‑time
- Fediverse‑ready
- Easy to maintain
- Perfect for your ecosystem
- A massive upgrade from SMF
- Future‑proof
And it fits exactly into the migration plan we built.
The higher use sites (like the forum) will end up going on a managed plan so we have better resources when there are issues. Since I'll be doing some of the building I am hoping I will have a better understanding of how all of the magical gremlins work, and either fix stuff or be able to better pinpoint issues for Micah, or better yet, release the automatic server monkeys to deal with issues for us.
Micah is an extremely valuable resource and we have used him very heavily over the years, but the man deserves to have a life, and his day job is already overworking him, so the less pressure that we can put on him, the more likely it is he will start to enjoy his life again.

This should future proof us (hopefully) until our 30th Anniversary.
Def
-
I'm happy to hear that things are moving towards the upgrade

-
Honestly, it should have been done before now, but due to a lack of competence on my part, a lack of time on Micah's and the difficulties involved in finding a server company I can trust, it just hasn't been possible until now.
It also won't be cheap running two servers (technically three) for at least three months, but in the end it will be worth it.
Def
-
-
So we are going to migrate SAKWiki from running in Tikiwiki to Mediawiki - Is that correct?
Is Tikiwik content compatible with Mediawiki? ie
All the format commands such as highlights, bolding, italics, numbered lists, bulleted lists, divider panels, columns, page layout etc?
Are the image galleries organised in the same way?
Are all the image display commands compatible? ie Display, descriptions, positioning on the screen, display on screen vs link to image etc?
Will all the hyperlinks work internal and external?Or is there some migration tool?
And basically the comments from my post above -
The usability, user-friendliness of the Wiki has been massively transformed over the last 10 years
I hope that work was not all in vain! -
There is a migration tool.
I'll tell you now, these are never 100% and there will be some formatting issues and some straightening up to do, but it should get us most of the way there. All of the info and pictures should make it, and we will have everything backed up just in case.
It's a risk but the alternative is to potentially lose it all by running a lesser platform.
MediaWiki should be a good step up and insure the future of SAKWiki a lot better than TikWiki.
Def
-
The biggest issue we have both with upgrading and migrating the wikis is the way it stored images in the past, since discontinued even in the tikiwiki software, which is why we are not able to even upgrade it further than we have currently.
None of the automated migration tools have worked when I tried them, which means we need to do it manually.
there's a lot of things to consider on all the sites/platforms that we'll have to look closely on a case by case basis, and hope for the best...
Time is not our friend, but hopefully we can have some sort of interim dual platform to fully test.
-
Hmmmm
We have about 5000 images, 240 galleries (in a hierarchy tree with 5 roots) and about 800 Wiki pages
Average links on a Wiki page to other pages or images is probably around 25 - The tools page has 60
Could be a long night!
-
We have about 5000 images, 240 galleries (in a hierarchy tree with 5 roots) and about 800 Wiki pages
Average links on a Wiki page to other pages or images is probably around 25 - The tools page has 60
Could be a long night!
I am well aware. Perhaps as Grant suggested we may have to look at several smaller server options (to better control requirements, and limit the load of one setup taking them all down etc)
@Grant Lamontagne said:
On Hetzner:- A CX32 or CPX31 instance will handle your entire community easily
I have a Hetzner account and don't see those suggested package options available, but google does show some other results on other pages that reference them, so maybe those are legacy names.
We do have node.js on current setup, but I am not seeing a clear setup path for nodebb on our current package without a lot of command line stuff I am not 100% comfortable with doing myself without a lot more reading...
I fear this is going to be the entire Fediverse experience, lots of manual commandline stuff to get it all setup and working, without mentioning the migrations from other environments.
-
I have just taken the first step and created an account on the new server company. As soon as it is set up I will put together a NodeBB install. Once I have something worth sharing I will let you all in to start playing around with it.
This does not officially start the 3 month plan posted above, but getting the most basic server account costs almost nothing, and that should be suitable for setup and testing. There's a good chance once we are ready to take it live that we will nuke it and start fresh, so once you are in, feel free to try to break everything.
Def
-
Here's the start if the new build. Expect changes as we go!
https://nodebb-2yel3-u73921.vm.elestio.app/
Def
-
Grant, if you were actually rewriting the fabric of reality from a terminal window, trust me — the logs would look way weirder than NodeBB plugin warnings. You’d be seeing things like:
info: destabilizing local spacetime mesh warn: agent 'Neo' detected outside expected parameters fatal: deja_vu_event(cat) triggered — rerouting timelineWhat you’re seeing now is just JavaScript being dramatic.
But here’s the fun part:
If this were the Matrix, you’d absolutely be the guy who figures it out because the forum software starts acting suspicious.And would I tell you?
I’d tell you the same thing Morpheus would tell you — with a straight face and a little too much gravitas:
“You’ve felt it your entire life. That there’s something wrong with the world.
You don’t know what it is, but it’s there.”But no, you’re not altering the source code of reality.
You’re just watching NodeBB boot in verbose mode, which is basically the same vibe but with fewer trench coats.When it finishes, we’ll get your admin account sorted and you’ll be back in control of your digital universe.
Just say the word when the scrolling stops.
Good to know... I'll just keep following the white rabbit.
Def
-
After spending the last two days trying to bring that forum online, I have encountered multiple failures.
I'll keep hacking away at it today- I'm going to try a clean install after fighting with the software version provided by the server company, which seems to have been stripped down and stuck on some files that weren't available.
Or some such nonsense.
Def
-
Sorry you are having issues with it. I wish I could be of help but I'm not very knowledgeable when it comes to that stuff.
I'm sure you'll get it figured out

-
I am not knowledgeable either. There is a reason Micah does most of this stuff! :ahhh
But CoPilot has given me the confidence and support I need to achieve greater and more in depth smurfups than I could have ever dreamed of.
And, it's not an active site that we are depending on, so it doesn't matter how badly it gets screwed up, so that makes me a little more adventurous too.
I'd never do this on MTO, SAKWiki etc. I'm just trying to lay the groundwork so we don't waste Micah's time later, when it comes to important stuff.
Def
-
Okay, if you need some help smurfing it up I can help with that

Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login