1 files changed, 6 insertions, 0 deletions
diff --git a/README.md b/README.md
index cdd4127..c440c49 100644
--- a/README.md
+++ b/README.md
@@ -70,6 +70,12 @@ GOOS=linux GOARCH=amd64 go build -o myapp
 ship --binary ./myapp --domain api.example.com
 ```
+On first deployment, Ship creates a `.ship/` directory in your current working directory containing:
+- `.ship/service` - systemd unit file
+- `.ship/Caddyfile` - Caddy reverse proxy config
+These files are uploaded on each deployment. You can edit them locally to customize your deployment (add extra Caddy routes, adjust systemd settings). The systemd service is regenerated when you update resource limits with `--memory`, `--cpu`, or `--args` flags. The Caddyfile is never regenerated, so your custom routes won't be overwritten.
 You can version control `.ship/` or add it to `.gitignore` — it's your choice.
 ## Commands

diff --git a/README.md b/README.md index cdd4127..c440c49 100644 --- a/README.md +++ b/README.md
@@ -70,6 +70,12 @@ GOOS=linux GOARCH=amd64 go build -o myapp
70	ship --binary ./myapp --domain api.example.com	70	ship --binary ./myapp --domain api.example.com
71	```	71	```
72		72
		73	On first deployment, Ship creates a `.ship/` directory in your current working directory containing:
		74	- `.ship/service` - systemd unit file
		75	- `.ship/Caddyfile` - Caddy reverse proxy config
		76
		77	These files are uploaded on each deployment. You can edit them locally to customize your deployment (add extra Caddy routes, adjust systemd settings). The systemd service is regenerated when you update resource limits with `--memory`, `--cpu`, or `--args` flags. The Caddyfile is never regenerated, so your custom routes won't be overwritten.
		78
73	You can version control `.ship/` or add it to `.gitignore` — it's your choice.	79	You can version control `.ship/` or add it to `.gitignore` — it's your choice.
74		80
75	## Commands	81	## Commands