jchomaz/Vulture
1
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Utilisation de compose plutot que de script pour builder, lancer et stopper les containers (maj de la doc)

Browse Source
This commit is contained in:
Laurent Ollagnier
2026-02-03 13:14:02 +01:00
parent 31649435a6
commit 013d629625
13 changed files with 120 additions and 230 deletions
Download Patch File Download Diff File Expand all files Collapse all files

118
VContainers/README.md
View File

@@ -3,94 +3,100 @@
Construction et lancements des containers.
Toutes les commandes sont à taper depuis la racine du dépôt.
## Upgrade :
```bash
git pull
podmane-compose build
systemctl --user restart vulture-stack.service
pkill -u vulture cage
```
## Build
```bash
./VContainers/build.sh
```
Ou manuellement :
```bash
podman build . -f ./VContainers/VNode/Containerfile -t vnode
podman build . -f ./VContainers/VApp/Containerfile -t vapp
podman-compose build
```
## Run
### Mode Manuel avec Scripts
**Développement (localhost):**
```bash
./VContainers/run_dev.sh
```
**Production (IP 192.168.73.252):**
```bash
./VContainers/run_prod.sh
```
Les containers sont lancés sur le réseau bridge `vulture-net` :
- **nanomq** : Broker MQTT (ports 1883, 9001, 8081, 8083, 8883)
- **vnode** : Services Node.js backend
- **vapp** : Frontend Vue.js (port 8080)
`podman-compose up -d`
## Stop
```bash
./VContainers/stop.sh
```
`podman-compose down`
Ou manuellement :
```bash
podman stop vapp vnode nanomq
podman network rm vulture-net
```
## Installation
## Lancement automatique avec Quadlet
### Automatisation au boot (User Mode)
Copier les fichiers du répertoire `quadlet` vers `~/.config/containers/systemd/`
#### Étape A : Activer la persistance de l'utilisateur
Par défaut, Fedora tue les processus utilisateurs à la déconnexion. On active le "lingering" pour que vos containers tournent dès le boot :
```bash
cp ./VContainers/quadlet/*.network ~/.config/containers/systemd/
cp ./VContainers/quadlet/*.container ~/.config/containers/systemd/
sudo loginctl enable-linger $USER
```
#### Étape B : Créer l'unité Systemd
Créez le dossier pour les services utilisateurs : `mkdir -p ~/.config/systemd/user/`
Créez le fichier ~/.config/systemd/user/vulture-stack.service :
```TOML
[Unit]
Description=Vulture Project Stack (Podman Compose)
After=network-online.target
[Service]
Type=simple
WorkingDirectory=%h/Vulture
# Lancement au boot
ExecStart=/usr/bin/podman-compose up
# Arrêt propre
ExecStop=/usr/bin/podman-compose down
Restart=always
[Install]
WantedBy=default.target
```
**Pour l'environnement de développement :**
#### Étape C : Activer le service
```bash
systemctl --user daemon-reload
systemctl --user enable --now nanomq.service
systemctl --user enable --now vnode.service
systemctl --user enable --now vapp_dev.service
systemctl --user enable vulture-stack.service
systemctl --user start vulture-stack.service
```
**Pour l'environnement de production :**
## Surveillance des Containers (Backend)
Puisque la stack tourne en mode utilisateur via Systemd, les commandes standard doivent être préfixées par `--user`.
* **Vérifier l'état de la stack :**
```bash
systemctl --user daemon-reload
systemctl --user enable --now nanomq.service
systemctl --user enable --now vnode.service
systemctl --user enable --now vapp_prod.service
systemctl --user status vulture-stack.service
```
**Vérifier le statut :**
* **Consulter les logs en temps réel (équivalent `tail -f`) :**
```bash
systemctl --user status nanomq.service vnode.service vapp_dev.service
journalctl --user -u vulture-stack.service -f
```
**Arrêter les services :**
* **Redémarrer proprement toute la stack :**
```bash
systemctl --user stop vapp_dev.service vnode.service nanomq.service
systemctl --user disable vapp_dev.service vnode.service nanomq.service
systemctl --user restart vulture-stack.service
```
## Configuration
Les fichiers de configuration se trouvent dans `VContainers/VApp/config/` :
- `config_dev.js` : Configuration développement (MQTT sur localhost)
- `config_prod.js` : Configuration production (MQTT sur 192.168.73.252)
Vous pouvez modifier ces fichiers selon vos besoins. En mode manuel, redémarrez les containers. Avec Quadlet, redémarrez le service correspondant :
* **Lister les containers actifs :**
```bash
systemctl --user restart vapp_dev.service
podman ps
```
## Tip

19
VContainers/quadlet/nanomq.container
View File

@@ -1,19 +0,0 @@
[Unit]
Description=Broker MQTT NanoMQ
Wants=network-online.target
After=network-online.target
[Container]
Image=docker.io/emqx/nanomq:latest
ContainerName=nanomq
Network=vulture-net.network
PublishPort=1883:1883
PublishPort=9001:9001
PublishPort=8081:8081
PublishPort=8083:8083
PublishPort=8883:8883
Volume=%h/Src/Fablab/Vulture/VContainers/MQTT/config/nanomq.conf:/etc/nanomq.conf:Z
Exec=--conf /etc/nanomq.conf
[Install]
WantedBy=default.target

12
VContainers/quadlet/vapp.container
View File

@@ -1,12 +0,0 @@
[Unit]
Description=Application Node.js VApp
Requires=vulture.pod
After=vulture.pod
[Container]
Image=localhost/vapp:latest
ContainerName=vapp
Pod=vulture
[Install]
WantedBy=vulture.pod

16
VContainers/quadlet/vapp_dev.container
View File

@@ -1,16 +0,0 @@
[Unit]
Description=Application Vue.js VApp (DEV)
Wants=network-online.target
After=network-online.target
Requires=nanomq.service
After=nanomq.service
[Container]
Image=localhost/vapp:latest
ContainerName=vapp
Network=vulture-net.network
PublishPort=8080:80
Volume=%h/Src/Fablab/Vulture/VContainers/VApp/config/config_dev.js:/usr/share/nginx/html/config.js:Z
[Install]
WantedBy=default.target

16
VContainers/quadlet/vapp_prod.container
View File

@@ -1,16 +0,0 @@
[Unit]
Description=Application Vue.js VApp (PROD)
Wants=network-online.target
After=network-online.target
Requires=nanomq.service
After=nanomq.service
[Container]
Image=localhost/vapp:latest
ContainerName=vapp
Network=vulture-net.network
PublishPort=8080:80
Volume=%h/Src/Fablab/Vulture/VContainers/VApp/config/config_prod.js:/usr/share/nginx/html/config.js:Z
[Install]
WantedBy=default.target

14
VContainers/quadlet/vnode.container
View File

@@ -1,14 +0,0 @@
[Unit]
Description=Application Node.js VNode
Wants=network-online.target
After=network-online.target
Requires=nanomq.service
After=nanomq.service
[Container]
Image=localhost/vnode:latest
ContainerName=vnode
Network=vulture-net.network
[Install]
WantedBy=default.target

6
VContainers/quadlet/vulture-net.network
View File

@@ -1,6 +0,0 @@
[Unit]
Description=Reseau Bridge pour Vulture
[Network]
NetworkName=vulture-net
Driver=bridge

14
VContainers/quadlet/vulture.pod
View File

@@ -1,14 +0,0 @@
[Unit]
Description=Pod Vulture pour le Broker MQTT et les Applications Node
Wants=network-online.target
After=network-online.target
[Pod]
# Mappings de ports : Host:Container (ces ports sont partagés par tous les conteneurs)
PublishPort=8080:80
PublishPort=1883:1883
PublishPort=8083:8083
PublishPort=8883:8883
[Install]
WantedBy=default.target

33
VContainers/run_dev.sh
View File

@@ -1,33 +0,0 @@
#!/bin/bash
set -e
# Move to repository root
cd "$(dirname "$0")/.."
NETWORK_NAME="vulture-net"
echo "Creating network $NETWORK_NAME..."
if podman network exists $NETWORK_NAME; then
echo "Network $NETWORK_NAME already exists."
else
podman network create $NETWORK_NAME
fi
echo "Starting NanoMQ..."
# NanoMQ needs to expose ports for external access (e.g. VApp frontend) and be on the network for VNode
podman run -dt --rm --network $NETWORK_NAME --name nanomq \
-p 1883:1883 -p 9001:9001 -p 8081:8081 -p 8083:8083 -p 8883:8883 \
-v ./VContainers/MQTT/config/nanomq.conf:/etc/nanomq.conf:Z \
docker.io/emqx/nanomq:latest --conf /etc/nanomq.conf
echo "Starting VNode..."
# VNode connects to nanomq via the network, no ports needed on host unless for debugging
podman run -dt --rm --network $NETWORK_NAME --name vnode vnode:latest
echo "Starting VApp (DEV CONFIG)..."
# VApp (nginx) needs port 5173 exposed
podman run -dt --rm --network $NETWORK_NAME --name vapp -p 5173:5173 \
-v ./VContainers/VApp/config/config_dev.js:/usr/share/nginx/html/config.js:Z \
vapp:latest
echo "All containers started on network $NETWORK_NAME with DEV configuration."

33
VContainers/run_prod.sh
View File

@@ -1,33 +0,0 @@
#!/bin/bash
set -e
# Move to repository root
cd "$(dirname "$0")/.."
NETWORK_NAME="vulture-net"
echo "Creating network $NETWORK_NAME..."
if podman network exists $NETWORK_NAME; then
echo "Network $NETWORK_NAME already exists."
else
podman network create $NETWORK_NAME
fi
echo "Starting NanoMQ..."
# NanoMQ needs to expose ports for external access (e.g. VApp frontend) and be on the network for VNode
podman run -dt --rm --network $NETWORK_NAME --name nanomq \
-p 1883:1883 -p 9001:9001 -p 8081:8081 -p 8083:8083 -p 8883:8883 \
-v ./VContainers/MQTT/config/nanomq.conf:/etc/nanomq.conf:Z \
docker.io/emqx/nanomq:latest --conf /etc/nanomq.conf
echo "Starting VNode..."
# VNode connects to nanomq via the network, no ports needed on host unless for debugging
podman run -dt --rm --network $NETWORK_NAME --name vnode vnode:latest
echo "Starting VApp (PROD CONFIG)..."
# VApp (nginx) needs port 5173 exposed
podman run -dt --rm --network $NETWORK_NAME --name vapp -p 5173:5173 \
-v ./VContainers/VApp/config/config_prod.js:/usr/share/nginx/html/config.js:Z \
vapp:latest
echo "All containers started on network $NETWORK_NAME with PROD configuration."

11
VContainers/stop.sh
View File

@@ -1,11 +0,0 @@
#!/bin/bash
echo "Stopping containers..."
podman stop vapp || echo "vapp not running"
podman stop vnode || echo "vnode not running"
podman stop nanomq || echo "nanomq not running"
echo "Removing network..."
podman network rm vulture-net || echo "Network vulture-net not found"
echo "Cleanup complete."

9
VContainers/upgrade.sh Executable file
View File

@@ -0,0 +1,9 @@
#!/bin/bash
set -e
# Move to repository root
cd "$(dirname "$0")/.."
git pull
./VContainers/build.sh
systemctl --user restart vulture-stack