Closed xiaods closed 1 month ago
Thanks for your points!
Thank you very much! Cheers!
Update:
Update:
- Wiki has been updated. Also README in ztm repo has been updated.
- ZTMesh v0.0.2 has MacOS(arm64/x64) and Windows(x64). In next release, we'll provide more artifacts of Linux and mobile.
I will double check later. thanks
hi, came across another issue on client side and there is confuse for me.
I am not sure wether i need do all cli step and graph ui step together? my environment is two server:
hi, came across another issue on client side and there is confuse for me.
---> Seems pipy didn't start correctly, so you can't configure mesh.
I am not sure wether i need do all cli step and graph ui step together? my environment is two server:
---> In "Join the mesh" section of wiki, I provide two different examples by using cli and gui. Cli is for servers which don't have desktop, and gui is for desktop OS(like MacOS or Windows). In fact, you can run a ztm agent by cli or gui. It both works.
- aws server, setting role is ztm hub and backend server.
-----> Run CA server, Hub, "Join the mesh by Cli". All steps in command line.
- my local mac, as client server, don't know what step should be do step by step.
----> Both cli and gui work. I recommend GUI. And it's better to use GUI as mesh admin.
Hope I've answered your questions. Feel from to drop further questions here. Cheers!
hi, came across another issue on client side and there is confuse for me.
---> Seems pipy didn't start correctly, so you can't configure mesh.
I am not sure wether i need do all cli step and graph ui step together? my environment is two server:
---> In "Join the mesh" section of wiki, I provide two different examples by using cli and gui. Cli is for servers which don't have desktop, and gui is for desktop OS(like MacOS or Windows). In fact, you can run a ztm agent by cli or gui. It both works.
- aws server, setting role is ztm hub and backend server.
-----> Run CA server, Hub, "Join the mesh by Cli". All steps in command line.
- my local mac, as client server, don't know what step should be do step by step.
----> Both cli and gui work. I recommend GUI. And it's better to use GUI as mesh admin.
Hope I've answered your questions. Feel from to drop further questions here. Cheers!
thanks, let me double check again
@keveinliu I already double check my environment with ZTM and pipy.
because the pipy is not working on MacOS Intel version. the pipy link is come from here: pipy-ztm-v0.0.2-macos-x64.zip
the pipy issue also caused the ZTM graph app is not working on my environment. please double check. thanks a lot.
After repeatedly reading the tutorial, I believe that there are many redundant steps in the current tutorial. Some steps do not clearly state the commands, which leads to the need for alignment of content and causes confusion for novice users. I think that the scenario plan should be one-click through to the end, without interrupting novice users. A tutorial that allows users to follow step by step and achieve success is what is needed. The current tutorial cannot achieve this. Based on the current situation, I suggest that you revise it using large model services such as ChatGPT. There are also many English descriptions that are not clear to understand. Please use ChatGPT4o to help you correct them. It will only take a few seconds. Thank you.
I am also confuse why came across this issue. please help me
another case: in windows 10 env:
with my dig info. it works like a charm.
Conclusion: ztm need pipy engine. so through the wiki guide, only the below cmd is valid:
$ arch=`uname -m`
$ wget https://pipy-oss-1255617643.cos-website.ap-beijing.myqcloud.com/repo/pipy/${arch}/binary/pipy-1.1.0-33-generic_linux-${arch}.tar.gz
$ tar xvf pipy-1.1.0-33-generic_linux-${arch}.tar.gz && sudo cp -f usr/local/bin/pipy /usr/local/bin && rm -fr usr
and the ztm project's release page attach all invalid packag. https://github.com/flomesh-io/ztm/releases/tag/v0.0.2 i have also check the status:
I finally succeeded by browsing the design principles of ZTM on the wiki and using the ZTM source code repository to make the call.
/close by resolved.