@akash-chowdhury-24/deployhub 2.0.39 → 2.0.41

package/README.md

@@ -765,7 +765,7 @@ SSH-based deploys (`ssh`, `ec2`, `azure-vm`, `gcp-vm`, and `docker` with `remote
 
 Commands run over the **existing** SSH session (not a second connection), unless a successful hook sets `"reconnect": true`. Kubernetes and Docker `local` / `raw` modes do not support hooks (no persistent remote shell session); configuring them there fails loudly at deploy/rollback.
 
-On docker-ssh, `postDeploy` runs **after** the port-publish inspect check (`docker inspect` confirms `0.0.0.0:<port>->`). A hook that curls the app's published port therefore sees a container DeployHub already treated as published. If that inspect fails, `postDeploy` does not run.
+On docker-ssh, `preDeploy` / `rollback` run **before** remote registry login and `docker stop`/`run`, so a hook can install Docker on a bare host. `postDeploy` runs **after** the port-publish inspect check (`docker inspect` confirms `0.0.0.0:<port>->`). A hook that curls the app's published port therefore sees a container DeployHub already treated as published. If that inspect fails, `postDeploy` does not run.
 
 Hook `command` strings are raw remote shell — there is **no** `{{buildId}}` / `{{containerName}}` / `{{port}}` / `{{environment}}` substitution. Hardcode values per environment (or read them from the remote environment). Extra Docker environments use an env-scoped container name (`{project}-{env}`; the first/grandfathered env stays `{project}`), so a hook that `docker exec myapp …` on staging will miss `myapp-staging`.
 
@@ -830,6 +830,8 @@ sudo chown your-ssh-user:your-ssh-user /var/www/your-app-name
 
 Replace `/var/www/your-app-name` with your actual deploy path and `your-ssh-user` with your configured `SSH_USER` (e.g. `ec2-user` on Amazon Linux, `ubuntu` on Ubuntu). Without this, DeployHub cannot write your build output — `deployhub doctor` will catch it and show the exact fix.
 
+**Manually placed files (`.env`, etc.):** SSH / EC2 / Azure VM / GCP VM redeploy and rollback do **not** wipe the deploy directory. Extraction uses `unzip -o` (fullstack: `rsync -a` with no `--delete`) so only files present in the artifact are added or overwritten; a `.env` you place on the server yourself is left untouched. Keep secrets out of the zip. Docker-SSH is container-based and does not use this directory extract.
+
 **Frontend deploys** that auto-activate `nginx.conf` also need **passwordless sudo** for Nginx test/reload (and `cp` into `/etc/nginx/`). After installing Nginx, run `sudo visudo` and add a line like:
 
 ```bash
@@ -853,6 +855,8 @@ sudo usermod -aG docker your-ssh-user
 
 Then **reconnect** (group membership applies on the next login). `deployhub doctor` reports this if missing (it prints the exact `usermod` line). See [Docker](#docker) below.
 
+You can also put that bootstrap in **preDeploy hooks** on a bare host (install Docker, `usermod`, `"reconnect": true`). Registry login runs **after** preDeploy, so those hooks get a chance to install `docker` before `docker login`. Failed login used to abort first (`docker: command not found`) and skip the hooks.
+
 ### SSH
 
 **Verification:** Real-world verified DEPLOY and ROLLBACK.
@@ -902,7 +906,7 @@ Then **reconnect** (group membership applies on the next login). `deployhub doct
 - [ ] Docker installed (`docker --version` works) — on this machine / CI for **local** and **raw**; on the remote Linux host for **ssh**
 - [ ] Registry account if pushing private images
 - [ ] `docker-compose.yml` in project if you use multi-service Compose (not auto-generated)
-- [ ] **SSH mode only:** [one-time server setup](#one-time-server-setup-before-your-first-deploy) — Docker on the host and the SSH user in the `docker` group (`sudo usermod -aG docker <user>`, then reconnect)
+- [ ] **SSH mode only:** [one-time server setup](#one-time-server-setup-before-your-first-deploy) — Docker on the host and the SSH user in the `docker` group (`sudo usermod -aG docker <user>`, then reconnect). A `preDeploy` hook can install Docker and run that `usermod` with `"reconnect": true`; registry login happens after preDeploy.
 
 `init` and `env add` ask **Where should the container run?**
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@akash-chowdhury-24/deployhub",
-  "version": "2.0.39",
+  "version": "2.0.41",
   "description": "Zero-configuration deployment and artifact manager",
   "type": "module",
   "main": "./src/cli/index.js",

package/src/deployment/providers/docker.js

@@ -167,6 +167,13 @@ export function createDockerProvider(config, envName, env = process.env) {
       const registryToken = imageEnv.DOCKER_REGISTRY_TOKEN || '';
       const registryUrl = imageEnv.DOCKER_REGISTRY_URL || '';
 
+      ssh = await runDeployHooks({
+        session,
+        ssh,
+        settings,
+        stage: isRollback ? 'rollback' : 'preDeploy',
+      });
+
       if (registryUser && registryToken) {
         const registry = registryUrl || 'https://index.docker.io/v1/';
         log.info('Logging in to container registry on remote host...');
@@ -177,13 +184,6 @@ export function createDockerProvider(config, envName, env = process.env) {
         );
       }
 
-      ssh = await runDeployHooks({
-        session,
-        ssh,
-        settings,
-        stage: isRollback ? 'rollback' : 'preDeploy',
-      });
-
       await session.exec(ssh, cmds.stop);
       await session.exec(ssh, cmds.rm);
       await session.exec(ssh, cmds.pull, {