File

tools/migration/migrator.cfg.lua @ 12813:4be161c25e14

net.resolvers.service: Fix reporting of Bogus DNSSEC results The order of checks led to Bogus results being reported with a generic "unable to resolve service". This had no practical effects as such results are simply empty and the process would stop there. Tested by attempting to establish s2s with dnssec-bogus.sg and observing the error reply.
author Kim Alvefur <zash@zash.se>
date Wed, 21 Dec 2022 23:46:37 +0100
parent 12168:33e856c65033
child 13295:b788307ca06a
line wrap: on
line source

local data_path = "../../data";

local vhost = {
	"accounts",
	"account_details",
	"roster",
	"vcard",
	"private",
	"blocklist",
	"privacy",
	"archive-archive",
	"offline-archive",
	"pubsub_nodes-pubsub",
	"pep-pubsub",
}
local muc = {
	"persistent",
	"config",
	"state",
	"muc_log-archive",
};

input {
	hosts = {
		["example.com"] = vhost;
		["conference.example.com"] = muc;
	};
	type = "internal";
	path = data_path;
}

output {
	type = "sql";
	driver = "SQLite3";
	database = data_path.."/prosody.sqlite";
}

--[[

input {
	type = "internal";
	path = data_path;
}
output {
	type = "sql";
	driver = "SQLite3";
	database = data_path.."/prosody.sqlite";
}

]]