Chris,

I have modified the UPDATE_SQL_en.mojo document.
There should be no issues arising from the previous git-related
complaints; with the new guide, this should no longer happen.

No user files are deleted. The update only incorporates the necessary
modules that provide greater flexibility in data consolidation.
This is important because reverting to the official mojo branch is
relatively straightforward. Even so, it is always important to make a
backup of /spider beforehand.

Regarding the connection to EA3CV-3, that was my mistake.
I am migrating multiple services between VPSs, and I believe I did not
export your data.
It is a tedious process, as everything needs to be rebuilt to ensure a
clean and properly structured setup on a single VPS.

Please send a direct email with your configuration details and
password.

Kin EA3CV

De: Christopher <dxspider-support@dxcluster.org>
Para: DXSpider <dxspider-support@dxcluster.org>
CC: Christopher <wi3w@wi3w.net>
Fecha: miércoles, 21 de enero de 2026 1:57 CET
Asunto: [Dxspider-support] Re: EA3CV-2 node - SQL backend

Hello Kin,

First off, thank you for this! I have had migrating to a database on my todo list for a long time. This makes things much easier. WI3W-3 is now on your dx-sql branch, testing. I had to rebuild WI3W-3 not that long ago and I had pulled the dxspider directory from your github. When I tried to transition to the dx-sql repo, I got an error about merging the two branches saying that they were essentially incompatible. Sorry I don't recall the exact error.

Second, I noticed that WI3W-3 lost connection to EA3CV-3 sometime in the early hours of the 20th. I have disabled the cronjob for now. Let me know if I need to do something other than what we have been doing.

73, Chris WI3W

From: Joaquin via Dxspider-support <dxspider-support@dxcluster.org>
Sent: Tuesday, January 20, 2026 4:10 AM
To: DXSpider support mailing list <dxspider-support@dxcluster.org>
Cc: Joaquin <joaquin@cronux.net>
Subject: [Dxspider-support] EA3CV-2 node - SQL backend

Hi all,

I have moved my EA3CV-2 node into production with a new implementation that allows using the traditional dbfile backend or alternatively MariaDB/MySQL or SQLite.

This makes it possible to keep the bad lists, filters, and user_json data stored in a database. Performance is extremely fast, and the system is fully reversible back to dbfile if needed.

You can find the project here: https://github.com/EA3CV/dx-sql

More to come…

73 de Kin EA3CV