Install
Installing NetLiNQ
The same NetLiNQ platform runs in both places. What differs is where the servers come from and what builds them — so the install guide you want is the one that matches your infrastructure.
Install on your own hardware
The installer builds the Kubernetes cluster on servers you provide, in your own data centre. Covers sizing, the vars file with a form that writes it for you, secrets, the installer run and what to check afterwards.
Install on AWS
Terraform and Terragrunt build the VPC, the EKS cluster, MongoDB Atlas and RDS in your own AWS account, then deploy the same platform on top. Covers secrets, inputs.hcl, the applies, private deployments and teardown.
Operate
Running it day to day
Lifecycle Service
Controlled shutdown and post-boot restore. How to arm the two systemd units, what happens at shutdown and at boot, the replicas.json order, and how to scale the platform down by hand.
Monitoring Guide
What the platform exposes and where to look when something is wrong — dashboards, logs and the health signals worth alerting on.
Maintain
Moving to a new release
Upgrades are run against the infrastructure underneath NetLiNQ, so each deployment target has its own operator guide. They are not interchangeable.
Upgrade on your own servers
Back up the running system, restore it into a staging cluster, promote staging to live. Includes the command reference, rollback and validation steps.
Upgrade on AWS
A second environment is built beside the running one and traffic moves across by DNS. Being written — the page sets out what it will cover and how to plan an upgrade with BLiNQ support in the meantime.
Reference
Which guide answers what
secretsctl reference.