feat(purchase): historical data capture for alpla purchase

backend/server.ts

@@ -10,6 +10,7 @@ import { createNotifications } from "./notification/notifications.master.js";
 import { monitorReleaseChanges } from "./opendock/openDockRreleaseMonitor.utils.js";
 import { opendockSocketMonitor } from "./opendock/opendockSocketMonitor.utils.js";
 import { connectProdSql } from "./prodSql/prodSqlConnection.controller.js";
+import { monitorAlplaPurchase } from "./purchase/purchase.controller.js";
 import { setupSocketIORoutes } from "./socket.io/serverSetup.js";
 import { baseSettingValidationCheck } from "./system/settingsBase.controller.js";
 import { createCronJob } from "./utils/croner.utils.js";
@@ -36,7 +37,7 @@ const start = async () => {
 	// also we always want to have long lived processes inside a setting check.
 	setTimeout(() => {
 		if (systemSettings.filter((n) => n.name === "opendock_sync")[0]?.active) {
-			log.info({}, "Opendock is not active");
+			log.info({}, "Opendock is active");
 			monitorReleaseChanges(); // this is od monitoring the db for all new releases
 			opendockSocketMonitor();
 			createCronJob("opendockAptCleanup", "0 30 5 * * *", () =>
@@ -44,6 +45,10 @@ const start = async () => {
 			);
 		}
 
+		if (systemSettings.filter((n) => n.name === "purchaseMonitor")[0]?.active) {
+			monitorAlplaPurchase();
+		}
+
 		// these jobs below are system jobs and should run no matter what.
 		createCronJob("JobAuditLogCleanUp", "0 0 5 * * *", () =>
 			dbCleanup("jobs", 30),