Skip to content

Tutorials#

Short, hands-on tutorials that build on each other. Each one starts from where the previous one ended, uses only real commands and configuration keys, and ends with a check you can run yourself.

Just want to see it run?

The Quick start builds manent and runs a deploy in five minutes. The tutorials explain what happens and why.

Learning path#

  • First deploy to a Linux server

    Release a tarball over SSH with one directory per version, simulate it with a dry-run, watch an automatic rollback and go back with a manual one.

    30 minutes · Docker, Go

  • Environments and secrets

    Move targets and parameters out of the descriptor into Consul, read the SSH key from Vault and limit what a descriptor may ask for.

    30 minutes · continues tutorial 1

  • Promotion, approvals and freezes

    Turn on authentication and roles, require that production only receives what passed through test, approve with a second person and freeze production during an incident.

    25 minutes · continues tutorial 2

  • Deploy to Kubernetes

    Release manifests or a Helm chart to a cluster with a namespaced service account, follow the rollout and roll back from the history kept in the cluster.

    30 minutes · a Kubernetes cluster

  • Progressive rollout with health gates

    Release a canary first, then one AZ at a time, with bake times, HTTP probes, a Prometheus error-rate gate, an approval after the canary and automatic rollback.

    30 minutes · Prometheus

  • Deploy from a CI pipeline

    Give CI a dedicated token and role, release from GitHub Actions or GitLab CI with an idempotent job, publish the outcome and gate configuration changes.

    20 minutes · GitHub or GitLab

  • Infrastructure and configuration in a chain

    An infrastructure deploy creates the VMs and exports their addresses, a configuration deploy imports them as targets: chained with --import, then from the release in service, with a broken export that stops the chain.

    25 minutes · continues tutorial 1

  • Run manent in production

    Postgres, several workers, OIDC sign-in, TLS, monitoring, SIEM and backups: the checklist to go from the laptop to a platform service.

    45 minutes · Kubernetes or VMs

Integrations#

Once the basics are in place, the Integrations section has a step-by-step guide for every external tool: Slack, Microsoft Teams, ServiceNow, Jira, GitHub Actions, GitLab CI, Terraform, Vault, Consul, identity providers, Prometheus and the other metrics systems, artifact repositories and SIEMs.

Conventions#

  • Commands are run from the tutorial directory, with manent and manent-server on the PATH.
  • Command output and logs are shown as manent prints them: in English.
  • Values to replace are written in angle brackets, for example <your-cluster>.