add fm fe

apps/fm-fe.yaml

@@ -0,0 +1,38 @@
+# gitops-demo child Application — now Helm-based, using the shared chart.
+#
+# MULTI-SOURCE explained: ArgoCD lets an Application pull from more than one
+# source. We use two, BOTH pointing at this same manifest repo:
+#   1. ref: values  — exposes the repo as "$values" so we can reference a file
+#                     from it (the per-service values.yaml).
+#   2. path: charts/app  — the generic chart, rendered with that values file.
+# This keeps the chart shared and each service's values in its own clean file,
+# instead of duplicating manifests or inlining values here.
+#
+# NOTE: replace REPLACE_WITH_MANIFEST_REPO_URL in BOTH sources with the real
+# repo URL (same as before — ArgoCD reads these straight from git).
+apiVersion: argoproj.io/v1alpha1
+kind: Application
+metadata:
+  name: fm-fe
+  namespace: argocd
+spec:
+  project: default
+  sources:
+    - repoURL: https://gitea.lgkentang.com/darren.maverick/k3s-manifests.git
+      targetRevision: HEAD
+      ref: values
+    - repoURL: https://gitea.lgkentang.com/darren.maverick/k3s-manifests.git
+      targetRevision: HEAD
+      path: charts/app
+      helm:
+        valueFiles:
+          - $values/fm-fe/dev/values.yaml
+  destination:
+    server: https://kubernetes.default.svc
+    namespace: dev
+  syncPolicy:
+    automated:
+      prune: true
+      selfHeal: true
+    syncOptions:
+      - CreateNamespace=true

fm-fe/dev/values.yaml

@@ -0,0 +1,11 @@
+name: fm-fe
+image:
+  repository: mybitlab/wfm
+  tag: fe-dev
+replicas: 2
+containerPort: 3000               # whatever port your API listens on
+ingress:
+  host: fm.dev.lgkentang.com
+  path: /                 # API traffic → backend
+  tls: true        
+  clusterIssuer: letsencrypt-prod