-
Notifications
You must be signed in to change notification settings - Fork 351
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
Before we run the examples, wechaty should be installed. #41
Comments
@kaffa Thanks for summary this for Windows developers! Would you like to share your experience on our Chatie Blog as a Windows User Tutorial? Because what you write will be very valuable for the community. If you agree, I'll send you a invitition on our Blog Repo. And I also noticed that you had published a blog about this on your Blog in Chinese, you can link back to your blog after you finished the Chatie Blog. |
Thanks! I would like to do that. |
@kaffa Thank you very much for accepting my invitation! Blog invitation had been sent from https://github.com/Chatie/blog/issues/91 |
Close this issue because @kaffa had published his blog post at https://blog.chatie.io/wechaty-installation-in-windows-10/ |
Wechaty installation is not so easy that it tooks me 4 hours to complete this simple task in Windows 10 Home Edition.
First, there're 2 ways to install wechaty, one is npm, the other is docker. Because docker needs at least Windows Proffesional to run in, we only have the first choice if we bought a home-use Windows and are not going to get the Windows Pro at $99.
Secondly, if we choose install it via npm way, some requirements and descriptions missed in the installation docs:
If we complete the 4 steps, wechaty runs!
Then, the QRCode in Windows Cmd Prompt is in a mess, I have to copy it from console to notepad and change the font setting to "Lucida Console", font-size 5, CTRL+A to reverse the color of the QRCode.
Finally, after I scaned it, the ding-dong-bot run, I sent a ding, it replied a dong. That was the story yestorday.
The text was updated successfully, but these errors were encountered: