Skip to content

Decouple bmon-infra deploy from infrastructure restart #3

@jamesob

Description

@jamesob

Certain bmon-server infrastructure often doesn't need to be restarted during deploys (e.g. db, redis). Specifically in the case of redis, we don't want to routinely restart the container because of the ephemeral nature of redis' storage.

Split out deployment for app containers (e.g. server-task-worker) from the more infra-based containers. This probably amounts to having separate systemd unit files for each "type" of process, perhaps:

  • Infra containers
    • db
    • redis
  • Grafan containers
    • grafana
    • prom
    • alertman
    • loki
  • bmon containers
    • web
    • server-task-worker

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions