-
Notifications
You must be signed in to change notification settings - Fork 2
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
Manual/tutorial wanted ;) #5
Comments
Hi, very happy of your interest about this project and wanted to get in touch with you since I've seen your post on "medium.com". I will try to help you at best. First of all, very minimal setup is :
(NB1 : Socketel is a very nice "toy", providing great enhancements and comfort over "regular" use, but it's not mandatory at all. I'm very pleased to see that you've got one) You may also run, from your Linux server, a "PyMoIP Gateway" that will allow you to connect to your "PyMoIP Server" from either WS or Telnet. First testing in telnet mode (Putty or MobaXterm) might help. It's also handling connection redirections if needed. From your first attempt, the file "arbo_defaultvar.py", under folder "arbo_teletel", is incorrect and does not contains any default value for key "Retour" (Back). All settable values in "PyMoIP Server" need to have a default setting. May be the file is empty or you're pointing to the wrong file. From your second attempt, it seems that the command for "PyMoIP gateway" is incomplete. You have listening ports for the gateway (both telnet & WS), and logpath - that's great, but nothing more. (You should have something between your "PyMoIP gateway" and your "PyMoIP server" instance otherwise, the gateway won't be able to make you reach anything.) I need to review a bit what I've already written in the wiki and I revert to you soon. |
Questions :
So far, I admit that nothing is present yet in the wiki about "PyMoIP Server" .... but
|
Thanks for the answer. Using without Socketel is even better, fewer components are required :)
It would be nice to have a connection diagram in the wiki and to see a general data flow, which file is responsible for what. |
In the wiki, something about 'PyMoIP User' : how to connect a minitel over serial ... just added points 1 and 6 at the moment. |
Added a PyMoIP/Docs folder with new drawio schematics about PyMoIP_User, PyMoIP_Gateway, and PyMoIP_Server. Also added an "old" word document focussed on PyMoIP_Gateway. ==> Let me know if that helps, if things are remaining unclear, typos, nonsences, whatever. |
Thanks, I will try :) |
Hi and thanks for the interesting project.
I have this hardware setup:
What is the minimum config I need, to run a local server and connect a Minitel to it?
I run a python3 -m Server command on my Ubuntu machine, I also specified a ws://10.14.24.110:8765 server in the Socketel config, I see the connection, but I got this error:
As a second attempt, I tried running python3 -m Gateway --tcp 9000 --ws 9001 --logpath . on the same machine, and specified the ws://10.14.24.110:9001 port in Socketel, I see only ValueError(f"invalid subprotocol: {subprotocol}") in the log.
What am I doing wrong?
Thanks.
The text was updated successfully, but these errors were encountered: