feat: add one-question VPS installer

README.md

@@ -26,7 +26,9 @@ WebSocket traffic always reach `tproxy-server`.
 
 ## Repository contents
 
+- `quick-install.sh` — fresh-VPS installation with Docker and automatic HTTPS;
 - `install.sh` — interactive installation on an existing Docker/NPM host;
+- `compose.quick.yml` and `Caddyfile` — optional Caddy frontend for the quick path;
 - `compose.yml` and `Dockerfile` — reproducible, checksum-pinned build;
 - `ingress/ingress.go` — canonical ingress used by new installations;
 - `ingress/ingress.js` — equivalent emergency implementation;
@@ -37,6 +39,32 @@ WebSocket traffic always reach `tproxy-server`.
 
 ## Installation
 
+### Quick installation on a fresh VPS
+
+Use a clean x86_64 VPS running Ubuntu or Debian. Create one direct DNS `A`
+record for the proxy hostname. Copy the HTTPS clone URL from the Gitea **Code**
+menu, connect to the VPS over SSH, and run:
+
+```sh
+sudo apt update
+sudo apt install -y git
+git clone <REPOSITORY_URL>
+cd telegram-web-proxy-stack
+sudo ./quick-install.sh
+```
+
+The script asks only for the hostname. It resolves the public IPv4 from DNS,
+installs Docker from Docker's official package repository, deploys the proxy and
+Caddy, obtains the TLS certificate, and prints the Telegram connection values.
+Inbound TCP ports 80 and 443 must be allowed by the VPS provider. This is a
+separate deployment mode and does not require Nginx Proxy Manager.
+
+Run `quick-install.sh` again after `git pull --ff-only` to update a quick
+installation. Do not switch that deployment to `install.sh`, which is intended
+for the Nginx Proxy Manager mode below.
+
+### Existing Docker host with Nginx Proxy Manager
+
 Requirements:
 
 - x86_64 Linux;