close
The Wayback Machine - https://web.archive.org/web/20210817100121/https://github.com/apache/shardingsphere/issues/11588
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explanation about %SHARDINGSPHERE_PROXY_HOME% in Docs #11588

Open
sgc109 opened this issue Jul 30, 2021 · 1 comment
Open

Explanation about %SHARDINGSPHERE_PROXY_HOME% in Docs #11588

sgc109 opened this issue Jul 30, 2021 · 1 comment

Comments

@sgc109
Copy link
Contributor

@sgc109 sgc109 commented Jul 30, 2021

In documentation for shardingsphere proxy, it says as follows

%SHARDINGSPHERE_PROXY_HOME% is the shardingsphere proxy extract path. for example: /Users/ss/shardingsphere-proxy-bin/

However, it is not clear for what "shardingsphere proxy extract path" means.
I just guessed that %SHARDINGSPHERE_PROXY_HOME% is shardingsphere/shardingsphere-distribution/shardingsphere-proxy-distribution/src/main/resources because this is one of few(6 exactly) places that include start.sh in bin/ directory in it, and the only place related with shardingsphere proxy at the same time.

But, when I run start.sh in shardingsphere/shardingsphere-distribution/shardingsphere-proxy-distribution/src/main/resources/bin, then following error occurs.

Error: Could not find or load main class org.apache.shardingsphere.proxy.Bootstrap

I think there need some correct explanations in documentation.

@menghaoranss
Copy link
Contributor

@menghaoranss menghaoranss commented Jul 30, 2021

shardingsphere proxy extract path is based on ShardingSphere's binary package,would you like to explain with a PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants