chore: add a docker compose file for standalone mode

[lmatz]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

add a docker-compose file for standalone mode. Will update the docs.

resolve #12538

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[fuyufjh]

LGTM

Actually, I think we can go one step further and use standalone mode in Docker by default. That is, instead of adding a new docker-compose-standalone.yaml, I think we can place the existing docker-compose.yaml, because that a user preferring docker-compose than k8s must want to deploy RW in a single machine.

But this may involve some modifications to test pipeline as well. Since the v1.4 is coming soon, we may do it later.

[kwannoel]

Thanks!

[codecov]

Codecov Report

Merging #13233 (1ebb91e) into main (57f75da) will increase coverage by 0.06%.
Report is 4 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #13233      +/-   ##
==========================================
+ Coverage   68.06%   68.13%   +0.06%     
==========================================
  Files        1515     1515              
  Lines      257111   257111              
==========================================
+ Hits       175013   175192     +179     
+ Misses      82098    81919     -179     

Flag	Coverage Δ
rust	68.13% <ø> (+0.06%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 17 files with indirect coverage changes

📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

[hengm3467]

LGTM

Actually, I think we can go one step further and use standalone mode in Docker by default. That is, instead of adding a new docker-compose-standalone.yaml, I think we can place the existing docker-compose.yaml, because that a user preferring docker-compose than k8s must want to deploy RW in a single machine.

But this may involve some modifications to test pipeline as well. Since the v1.4 is coming soon, we may do it later.

@lmatz Was this PR included in v1.4? I don't see it in the comparison list (1.3-rc - 1.4-rc). And I assume using the standalone mode in Docker by default is not done yet. Correct? Thanks.

[lmatz]

LGTM
Actually, I think we can go one step further and use standalone mode in Docker by default. That is, instead of adding a new docker-compose-standalone.yaml, I think we can place the existing docker-compose.yaml, because that a user preferring docker-compose than k8s must want to deploy RW in a single machine.
But this may involve some modifications to test pipeline as well. Since the v1.4 is coming soon, we may do it later.

@lmatz Was this PR included in v1.4? I don't see it in the comparison list (1.3-rc - 1.4-rc). And I assume using the standalone mode in Docker by default is not done yet. Correct? Thanks.

Hi @hengm3467,
It is not ready yet, and not included in v1.4. The default deployment of docker compose is still non-standalone mode.

We will need to do some tests first, details in
https://github.com/risingwavelabs/risingwave-docs/issues/1187