Installation

Installation#

docker run -d \
  --name MatchExec \
  -p 3000:3000 \
  -e TZ=UTC \
  -v $(pwd)/app_data:/app/app_data \
  -v $(pwd)/uploads:/app/public/uploads \
  ghcr.io/slamanna212/matchexec:latest

git clone https://github.com/slamanna212/MatchExec.git

cd MatchExec

docker compose up -d

helm install matchexec oci://ghcr.io/slamanna212/charts/matchexec

ingress:
  enabled: true
  className: nginx
  hosts:
    - host: matchexec.example.com
      paths:
        - path: /
          pathType: Prefix

metrics:
  serviceMonitor:
    enabled: true
    labels:
      release: kube-prometheus-stack  # match your Prometheus selector
  grafana:
    dashboardConfigMap: true  # auto-discovered by Grafana sidecar

Unraid#

Search for MatchExec in the Community Apps section of the Unraid Web Interface

Proxmox#

Until this project gets 500 Stars, MatchExec does not quality for Proxmox Helper Scripts, below is what will be submitted when it does qualify.

Paste this into your Proxmox shell. Follows all Proxmox Helper Script standards.

bash -c "$(curl -fsSL https://raw.githubusercontent.com/slamanna212/ProxmoxVED/refs/heads/feat/matchexec/ct/matchexec.sh)"

Running Dev Builds#

MatchExec has relatively stable dev builds. The dev releases are used as final testing before a full release.

You can run dev builds by using the dev docker tag for the Docker and Unraid install methods. For Docker Compose, clone the dev branch instead of main.

If you are using Kubernetes you will know how to run the dev branch.

Running from Source#

1. Clone the Repo
2. Install Node.js 24
3. npm install
4. npm run build (builds Next.js app + processes)
5. npm run migrate
6. npm run prod:start