docs: document --run-setup and --profile flags in deploy-to section
This commit is contained in:
11
README.md
11
README.md
@@ -232,6 +232,13 @@ on the remote.
|
||||
# Push everything (dotfiles + scripts):
|
||||
dotfiles deploy-to user@server
|
||||
|
||||
# After file transfer, also run setup_enterprise_ai_bash.sh on the remote
|
||||
# to create ~/workspace, ~/data, ~/models and write shell config:
|
||||
dotfiles deploy-to user@server --run-setup
|
||||
|
||||
# Specify a machine profile for the setup script (default: work):
|
||||
dotfiles deploy-to user@server --run-setup --profile work
|
||||
|
||||
# Scripts only (dotfiles_manager.sh, bootstrap.sh, setup script):
|
||||
dotfiles deploy-to user@server --scripts-only
|
||||
|
||||
@@ -251,6 +258,10 @@ Files are copied directly (not symlinked). Re-run `deploy-to` any time you
|
||||
want to push updates. `~/.ssh/` is skipped by default to avoid accidentally
|
||||
pushing private keys or your personal known_hosts to a shared server.
|
||||
|
||||
> **First-time setup on a server?** Use `--run-setup` to create the full
|
||||
> directory structure after file transfer, or answer `y` when prompted
|
||||
> interactively at the end of a normal `deploy-to` run.
|
||||
|
||||
### Centrally managing `~/.bashrc.local` for servers
|
||||
|
||||
Work servers can't reach the Gitea repo, so their `~/.bashrc.local` is managed
|
||||
|
||||
Reference in New Issue
Block a user