Skip to main content

DeployHub Agent

Agent distant officiel pour DeployHub.

DeployHub Agent s'installe sur le serveur qui héberge vos applications. Il se connecte à votre instance DeployHub par WebSocket, reçoit les jobs de déploiement, exécute les commandes configurées dans vos projets, remonte les logs en temps réel, puis renvoie le statut final du déploiement.

Ce paquet contient uniquement l'agent d'exécution. Il ne contient pas le backend DeployHub, le frontend, la base de données, ni les secrets de votre plateforme.

Installation avec pip

python3 -m pip install deployhub-agent

Les commandes suivantes sont installées :

deployhub-agent
deployhub-agent-run

Configuration

L'agent lit sa configuration depuis /etc/deployhub-agent/agent.env ou depuis les variables d'environnement.

Exemple de fichier /etc/deployhub-agent/agent.env :

AGENT_WS_URL="url_DeployHub/ws/agent"
AGENT_TOKEN="TOKEN_GENERE_DANS_DEPLOYHUB"
AGENT_WORKDIR="/var/www"
AGENT_RECONNECT_DELAY_SECONDS="5"
AGENT_HEARTBEAT_TIMEOUT_SECONDS="60"
AGENT_COMMAND_TIMEOUT_SECONDS="1200"

Lancez ensuite l'agent :

deployhub-agent-run

Installation complète comme service systemd

Pour une installation serveur complète sur Debian/Ubuntu, utilisez un environnement virtuel dédié, puis lancez install-service.

Exemple minimal :

sudo apt-get update
sudo apt-get install -y python3 python3-venv ca-certificates
sudo mkdir -p /opt/deployhub-agent
sudo python3 -m venv /opt/deployhub-agent/.venv
sudo /opt/deployhub-agent/.venv/bin/pip install --upgrade pip
sudo /opt/deployhub-agent/.venv/bin/pip install deployhub-agent

sudo /opt/deployhub-agent/.venv/bin/deployhub-agent install-service \
  --server url_DeployHub/ws/agent \
  --token "TOKEN_GENERE_DANS_DEPLOYHUB" \
  --workdir /var/www

Cette commande crée l'utilisateur système deployhub-agent, les dossiers /etc/deployhub-agent, /var/lib/deployhub-agent et /var/log/deployhub-agent, écrit le fichier /etc/deployhub-agent/agent.env, installe le service systemd, puis démarre l'agent.

Gestion du service

sudo systemctl status deployhub-agent
sudo journalctl -u deployhub-agent -f
sudo systemctl restart deployhub-agent

Permissions

L'agent exécute les commandes avec l'utilisateur du service systemd. Si vous utilisez l'utilisateur deployhub-agent, il doit avoir les droits nécessaires sur les dossiers de vos projets.

Exemple :

sudo chown -R deployhub-agent:deployhub-agent /var/www/mon-application

Pour un dépôt Git privé, configurez aussi l'accès Git pour cet utilisateur, par exemple avec une clé SSH de déploiement.

Metadata

Release files for deployhub-agent 1.0.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for deployhub-agent 1.0.3
File Size Uploaded Provenance
deployhub_agent-1.0.3.tar.gz 6.7 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for deployhub-agent 1.0.3
File Interpreter ABI Platform
deployhub_agent-1.0.3-py3-none-any.whl Python 3 none any Details

Total release size: 14.5 kB

Release files / deployhub_agent-1.0.3.tar.gz

Download URL deployhub_agent-1.0.3.tar.gz
Size 6.7 kB
Tags Source
SHA-256 checksum
How to use checksums
111ac524bdb05333e269633459637be4b0c590a540855e3f5892af04f11d3f5f
BLAKE2b-256 checksum
How to use checksums
e03455ea79b8cdd331ab17609e7a566af68ae2035769bc3755f2adb488e58520
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.10

Release files / deployhub_agent-1.0.3-py3-none-any.whl

Download URL deployhub_agent-1.0.3-py3-none-any.whl
Size 7.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
fedbaef430c6c4c78f1174a16549f53c1d476412632e46681285ad76f27becb6
BLAKE2b-256 checksum
How to use checksums
bd1b835d82fac67c1236b6529d9dd7e90f4991ce9d2b05582bc4d3160f471e6f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.12.10

Security for deployhub-agent 1.0.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

1.0.3 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page