-
Notifications
You must be signed in to change notification settings - Fork 114
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
How to create a Wechaty Token Gateway for Puppet XP #38
Comments
@keac You are running into I'd like to suggest that you can try to run $ node node_modules/wechaty/dist/esm/bin/io-client.js |
Thanks for the reporting, this issue is related to the Mixin dependencies (which will affect the start sequence/order) and should be fixed later. BTW: it would be great if you can copy/paste the TEXT log message here, instead of the image because the text will be great for searching and reading. |
|
The Please try this version (after it has been published to NPM around 10 mins after) and let me know the result, thanks! |
还是存在一样的问题
|
在执行
|
According to the below error message:
It seems that you have no Can you run |
We have switched to using the Please try the latest |
puppet-install.js 可以安装但是出现了新的问题
|
It seems that you are using an outdated NPM mirror/CDN/cache. Please disable any mirror/CDN/cache for your NPM and try again.
What's the new log message? |
另外我再次运行
|
使用npmmirror sync 同步了一下再安装解决可以正常运行了 感谢 |
It's great to know that your npm mirror has been synced. From the Please update your |
Now we have an official way to start Wechaty Token Gateway for Puppet XP: $ npm install -g [email protected] wechaty-puppet-xp
$ wechaty gateway --puppet wechaty-puppet-xp Related issue: |
环境变量设置无法生效
|
I have not test under windows, but it should work. If you can figure the problem out, I'd like to accept a PR to fix it. |
你好,我把这里的评论看过一次,但还是不太清楚怎么搭建一个wechaty-puppet-xp,然后用python连接,我现在的wechaty-puppet-xp是能运行成功的, |
TL;DR: All you need to run is:
Then by reading the output messages, you can find the published new token for your Python Wechaty program. |
is it means successly? and then now i need to have a available public ip ? |
Yes, it seems the gateway setup is successfully in your server. You need to have a public IP with firewall permissions if you want to use this token other than the local machine. |
ok, thank you very much, |
Yes you can. As you see the IP is 127.0.0.1 in the log message, that's because the Wechaty gateway detected that you have no any public IP, so it can not get an external IP. There will be two cases you need to deal with:
Please let me know if it works for you |
it is failed
|
Sad to know that. My suggestion is to try TypeScript of Wechaty and see if it works with TypeScript (you can refer to the getting started official docs at https://wechaty.js.org/docs/getting-started/). If the TS works then it means that the token gateway is in service, then you should file an issue in the Python Wechaty getting started repo. |
ok, Thank you for helping me with my big problem |
You are welcome, and I hope you can solve the big problem soon! |
Update Jan 15, 2022
Now we have an official way to start Wechaty Token Gateway for Puppet XP:
Related issue:
Abstract
We can create a Wechaty Token Gateway for wechaty-puppet-xp without any problem because all the Puppet in the Wechaty ecosystem will be able to support each other without any problem.
All Wechaty Puppet Providers can be converted to a Wechaty Puppet Service by using our Wechaty Token Gateway, which means the wechaty-puppet-xp can be converted as well.
The Problem
The only problem for using wechaty-puppet-xp with the token gateway is that currently in our docs, the token gateway is started by a docker command, but the wechaty-puppet-xp can not run inside a Linux docker.
The Solution
The solution would be to use Wechaty under your Windows system and start the token gateway manually, which you can learn how to do this from the Wechaty Dockerfile and this line from entrypoint.sh and this line from package.json:
TL;DR: start Wechaty Token Gateway manually with Windows:
Related issues
The text was updated successfully, but these errors were encountered: