SMSKing platform

Modernization workspace · operated by Laursen AS · built by Savellab

staging9c962d3

Live API

Fastify v2

Checking …

The v2 API surfaces the modernised endpoints. Legacy /api/* routes still answer for the existing dashboard.

/api/v2/healthOpenAPI docs ↗

Legacy site

Classic ASP

20 years of SMSKing.no

Customer pages stay unchanged during the strangler-fig migration. Routes below are served in-process by IIS; the v1 OpenAPI documents every legacy endpoint.

v1 OpenAPI docs ↗/login/register/send-sms/faq

Deploy pipeline

  1. 1Push to main → GitHub Actions builds the monorepo on Ubuntu.
  2. 2Self-hosted runner on this VM pulls the artifact.
  3. 3DB migrations → robocopy ASP → junction-swap Node deploys → smoke tests against IIS + Next.js + Fastify.
  4. 4NSSM-managed Windows services restart on demand and survive reboot; healthcheck cron pings /api/v2/health every minute.