refactor: migrate install/update orchestration from Bash to Python

.gitignore

@@ -1,4 +1,8 @@
 log
 dump.rdb
 hiddify_usages.json
-docker-data
+docker-data
+__pycache__/
+*.pyc
+.venv/
+.venv313/

README.md

@@ -184,6 +184,48 @@ When you want to share Telegram proxy or Shadowsocks proxy through other program
 </details>
 
 ## Installation and tutorials
+
+### Quick Start (New Python-based Manager)
+
+The new Python-based manager is the recommended way to install and manage Hiddify. It replaces the legacy Bash scripts (`install.sh`, `menu.sh`, `update.sh`).
+
+```bash
+# Clone the repository
+git clone https://github.com/hiddify/Hiddify-Manager.git /opt/hiddify-manager
+cd /opt/hiddify-manager
+
+# Run init.sh — it will install Python 3.13, set up a virtualenv, and launch the manager
+sudo bash init.sh
+```
+
+#### Available Commands
+
+| Command | Description |
+|---|---|
+| `./init.sh` | Launch the interactive menu |
+| `./init.sh install` | Run a full installation of all modules |
+| `./init.sh update` | Update Hiddify-Manager |
+| `./init.sh status` | Show system status |
+| `./init.sh migrate` | Migrate data from a legacy installation |
+| `./init.sh menu` | Launch the interactive menu |
+
+#### Migrating from a Legacy Installation
+
+If you have an existing installation at `/opt/hiddify-manager` (or `/opt/hiddify-server`), the migration tool will automatically detect it and copy your database, SSL certificates, acme.sh data, and configuration:
+
+```bash
+./init.sh migrate
+```
+
+For a custom legacy path:
+```bash
+python3 -m hiddify_manager.migrate --legacy-dir /path/to/old/install
+```
+
+Use `--dry-run` to preview changes without modifying anything.
+
+### Tutorials
+
 **Please find tutorial information on our website by clicking on image below.**
 
 <div align="center">

acme.sh/get_cert.sh

@@ -1,10 +1,7 @@
 #!/bin/bash
-cd $(dirname -- "$0")
-source cert_utils.sh
-#./lib/acme.sh --register-account -m my@example.com
-
-get_cert $1
-
-echo "cert installation is done."
-sleep 2
-stop_nginx_acme
+# Thin shim: the real ACME orchestration lives in
+# hiddify_manager.modules.cert_issuer. Kept as a .sh so commander.py
+# (panel-invoked via sudoers) can keep its absolute-path Command enum
+# without churning the panel side.
+cd "$(dirname -- "$0")/.."
+exec /opt/hiddify-manager/.venv313/bin/python -m hiddify_manager.modules.cert_issuer "$@"

apply_configs.sh

@@ -1,4 +1,11 @@
 #!/bin/bash
-cd $(dirname -- "$0")
-DO_NOT_INSTALL=true ./install.sh apply_configs $@
-#DO_NOT_INSTALL=true ./install.sh
+# Thin shim: panel hits /admin/actions/apply_configs which goes through
+# commander.py apply -> this script. Real impl lives in
+# hiddify_manager.manager.run_apply_configs.
+#
+# Log file (log/system/0-install.log, polled by the panel's
+# admin_log_api) is written by init.sh itself, not here — that way the
+# menu's "Reinstall" and a direct `./init.sh apply-configs` from the
+# shell get the same log file the panel expects.
+cd "$(dirname -- "$0")"
+exec ./init.sh apply-configs