From d91b45fc023b5b4a8ba93073d05e57a6a47b1626 Mon Sep 17 00:00:00 2001 From: Marc Wieland Date: Thu, 18 Jun 2026 12:38:23 +0000 Subject: [PATCH] docs(migration): note shell reload and browser restart after v1 upgrade Two steps that are easy to miss when moving from dde v1 and that make system:install or the TLS setup look broken: - After removing the v1 shell integration, the current session still has the v1 dde function loaded, so dde system:install keeps running against v1. Document restarting the shell (exec $SHELL -l works for zsh and bash). - mkcert's new root CA is only read by Firefox at startup, so a Firefox that was already open keeps showing .test sites as insecure until it is restarted. Signed-off-by: Marc Wieland --- docs/guides/migration-from-v1.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/guides/migration-from-v1.md b/docs/guides/migration-from-v1.md index dab9250..88ad11b 100644 --- a/docs/guides/migration-from-v1.md +++ b/docs/guides/migration-from-v1.md @@ -46,7 +46,8 @@ You can also run both commands in sequence — first `dde system:destroy`, then ### 2. Clean up shell configuration -Remove the dde v1 aliases and autocomplete from your `~/.zshrc` or `~/.bashrc`. +Remove the dde v1 aliases and autocomplete from your `~/.zshrc` or `~/.bashrc` and restart your shell. +If the shell was not restarted, `dde` still resolves to the old v1 commands, even after you have replaced the binary. Running `exec $SHELL -l` will do the trick as well. ### 3. Optionally remove v1 data @@ -76,7 +77,7 @@ dde project:up `project:init` creates the `.dde/` directory, detects your `docker-compose.yml`, and adds Traefik labels. It also strips v1 boilerplate (the explicit `dde` external network, the SSH-Agent volume mount and `SSH_AUTH_SOCK`, legacy `DDE_UID`/`DDE_GID` build args, fixed `container_name`) — in v2, networks and the SSH-Agent socket are injected by the runtime overlay, so the committed compose file stays clean. -Open `https://my-app.test` in your browser to verify. +Open `https://my-app.test` in your browser to verify. Firefox users may need to restart the browser to trust the certificate. #### .env file migration