- Add a NAS-specific frpc template that forwards to tuwen_web:80 over the compose network.
- Make docker-compose-Nas.yaml create tuwen_frpc by default instead of relying on Compose profiles, which Container Station may not enable.
- Remove host networking from the NAS frpc service so the tunnel works through Docker service DNS.
- Update README and Docker docs to explain the NAS frpc behavior and logs command.
- Rework docker-compose-Nas.yaml as a QNAP/NAS-friendly generic template with placeholders for NAS IP, public domain, proxy, and secrets.
- Preserve QNAP-specific fixes including relative build context, api network alias, NAS persistent paths, and 127.0.0.1 health checks.
- Keep optional frpc profile while avoiding real server addresses or tokens in the reusable template.
- Replace residual deployment examples with generic your-domain.example, NAS_IP, PROXY_IP, and LAN_CIDR placeholders in README and Docker docs.
- Make the default Docker Compose CORS_ORIGIN configurable so public and NAS deployments can override allowed origins without editing the compose file.
- Update the default frpc profile command to call frpc explicitly, matching the snowdreamtech/frpc entrypoint behavior observed in the deployed copy.
- Apply the same explicit frpc command to the NAS compose template.
- Keep real frpc server address and token from the deployed copy out of the reusable template.
- Add docker-compose-Nas.yaml for QNAP/威联通 deployment with NAS persistent data paths, API aliasing, and health checks tailored for NAS firmware.
- Parameterize NAS ports, data root, database credentials, proxy variables, CORS, session security, TRUST_PROXY, migrations, and seed settings.
- Include an optional frpc profile in the NAS compose file so port 4002 can be exposed through the existing frpc/frpc.toml workflow.
- Document NAS startup, health checks, public HTTPS settings, proxy settings, and frpc commands in README.
- Update Docker deployment documentation with the NAS compose workflow and the reminder to expose only 4002 publicly.
