Yicong-Huang opened a new issue, #5996:
URL: https://github.com/apache/texera/issues/5996

   ### Task Summary
   
   `bin/single-node/` ships the docker-compose deploy (compose file, env, 
examples profile, nginx + litellm config, README) but no wrapper script — users 
today have to `cd bin/single-node && docker compose --profile examples up`. 
After #5961 / #5994 landed `bin/local-dev.sh up | down | status | -i ...` for 
the native dev stack, the asymmetry is now: docker deploy = raw compose; native 
dev = polished wrapper.
   
   Add a parallel entry point so contributors get the same `bin/<deploy>.sh 
<verb>` shape:
   
   ```
   bin/
   ├── single-node.sh            # 3-line wrapper → bin/single-node/main.sh
   └── single-node/
       ├── main.sh               # engine
       ├── docker-compose.yml    (existing)
       ├── .env                  (existing)
       ├── litellm-config.yaml   (existing)
       ├── nginx.conf            (existing)
       ├── examples/             (existing)
       ├── README.md             (existing — update Launch section to point at 
the wrapper)
       └── tests/
           └── test_single_node_sh.sh
   ```
   
   Subcommands (minimal, mirrors the matching `local-dev.sh` verbs):
   
   * `bin/single-node.sh up` — pre-flight docker check, then `docker compose -f 
bin/single-node/docker-compose.yml --profile examples up -d`. Examples profile 
on by default (matches today's documented "Launch Texera" command). Tip block 
prints the dashboard URL + login.
   * `bin/single-node.sh down` — `docker compose ... down`. `--volumes` flag to 
drop volumes too.
   * `bin/single-node.sh status` (and no-arg) — `docker compose ps` rendered 
cleanly, with the same URL/log tip block.
   * `bin/single-node.sh logs <service>` — `docker compose logs -f <service>`.
   * `bin/single-node.sh --help` — usage reference.
   
   Bash 3.2 portable (macOS-friendly). License header + `find bin -name 
'test_*.sh'` CI discovery already cover this layout — no workflow edits needed. 
`bin/**` labeler glob already covers it too.
   
   `bin/single-node/main.sh` is implementation detail; only 
`bin/single-node.sh` appears in `--help`, error hints, status output, and the 
README's Launch section — same convention as `bin/local-dev.sh`.
   
   ### Task Type
   
   - [x] New Feature / Feature Request
   - [x] DevOps / Deployment / CI


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to