docs: complete README rewrite + cleanup stale mic-after-work refs in .env.example, DEPLOYMENT.md, QUICK_DEPLOY.md, DATABASE_CONFIG.md, AUDIT — delete backend_log.txt
Some checks failed
CI/CD Lions Pipeline / Build + Push + Deploy (push) Failing after 9s

This commit is contained in:
2026-04-24 19:38:29 +00:00
parent 770176092d
commit da2e763428
6 changed files with 182 additions and 8991 deletions

View File

@@ -97,7 +97,7 @@ Remplacez `<org>` par votre organisation Git (ex. `lionsdev`, `developer`) et `<
```bash
# Déploiement en dev (clone + build + image + déploiement K8s)
lionsctl pipeline \
-u https://git.lions.dev/<org>/mic-after-work-server-impl-quarkus-main \
-u https://git.lions.dev/<org>/afterwork-server-impl-quarkus \
-b develop \
-j 17 \
-e dev \
@@ -106,7 +106,7 @@ lionsctl pipeline \
# Déploiement en production sur le cluster k2
lionsctl pipeline \
-u https://git.lions.dev/<org>/mic-after-work-server-impl-quarkus-main \
-u https://git.lions.dev/<org>/afterwork-server-impl-quarkus \
-b main \
-j 17 \
-e production \
@@ -116,7 +116,7 @@ lionsctl pipeline \
# Avec déploiement Helm (charts générés automatiquement)
lionsctl pipeline \
-u https://git.lions.dev/<org>/mic-after-work-server-impl-quarkus-main \
-u https://git.lions.dev/<org>/afterwork-server-impl-quarkus \
-b develop \
-j 17 \
-e dev \
@@ -129,7 +129,7 @@ lionsctl pipeline \
| Option | Description | Exemple |
|--------|-------------|---------|
| `-u`, `--url` | URL du repo Git (obligatoire) | `https://git.lions.dev/.../mic-after-work-server-impl-quarkus-main` |
| `-u`, `--url` | URL du repo Git (obligatoire) | `https://git.lions.dev/.../afterwork-server-impl-quarkus` |
| `-b`, `--branch` | Branche à déployer | `develop`, `main` |
| `-j`, `--java-version` | Version Java (821) | `17` |
| `-e`, `--environment` | Environnement (dev / staging / production) | `dev`, `production` |
@@ -141,11 +141,11 @@ lionsctl pipeline \
### Vérification du déploiement
```bash
# Pods et statut (nom d'app dérivé du repo, ex. mic-after-work-server-impl-quarkus-main)
kubectl get pods -n applications -l app=mic-after-work-server-impl-quarkus-main
# Pods et statut (nom d'app dérivé du repo, ex. afterwork-server-impl-quarkus)
kubectl get pods -n applications -l app=afterwork-server-impl-quarkus
# Logs en temps réel
kubectl logs -n applications -l app=mic-after-work-server-impl-quarkus-main -f
kubectl logs -n applications -l app=afterwork-server-impl-quarkus -f
# Health check
curl https://api.lions.dev/afterwork/q/health/ready
@@ -307,7 +307,7 @@ spec:
### Étape 1 : Préparation
```bash
cd C:\Users\dadyo\PersonalProjects\mic-after-work-server-impl-quarkus-main
cd C:\Users\dadyo\PersonalProjects/lions-workspace/afterwork/afterwork-server-impl-quarkus
# Build Maven
mvn clean package -DskipTests
@@ -361,7 +361,7 @@ kubectl apply -f kubernetes/afterwork-service.yaml
kubectl apply -f kubernetes/afterwork-ingress.yaml
# Ou via lionsctl pipeline (clone + build + déploiement)
lionsctl pipeline -u https://git.lions.dev/<org>/mic-after-work-server-impl-quarkus-main -b develop -j 17 -e dev -c k1 -m <email>
lionsctl pipeline -u https://git.lions.dev/<org>/afterwork-server-impl-quarkus -b develop -j 17 -e dev -c k1 -m <email>
```
### Étape 5 : Vérification