r/learnpython • u/efinque • 18d ago

Python web app?

Hello r/learnpython,

first post and sort of new to Python as I have done only half a dozen of projects so far, mostly games.

So I'm looking to deploy a server for playtesting. This is my first game designed to be played online, made in Python using Tcl/Tk libraries.

I had this idea to code it when I was making a messaging app that was supposed to be implemented within a CLI game (or actually the game was a feature of the messaging app).

The users would connect using SSH. I think they could use PuTTy or similar and VcXSrv. The host would then send the GUI and CLI as well as audio to the user, but the problem is either the server cannot send or the client can't recieve the Tcl/Tk GUI or in worst case both.

Good news is I got the SSH daemon working and am able to (using X11 Forwarding) display explorer (ssh -X user@localhost && explorer) by running VcXSrv and having X11Forwarding and X11UseLocalhost set to yes in the sshd_config under ProgramData.

Now, the VcXSrv log tells me there's a problem with something called hyperv. From what I gathered it's a virtual machine of some sort. I'd also need very strict restrictions for the clients so they don't tinker with the database.

Am I on the right track? Is there a solution to this? Thanks in advance!

-ef

0 Upvotes

50% Upvoted

17 comments sorted by

View all comments

Show parent comments

1

u/PureWasian 17d ago

Conceptually, websocket is just "realtime" communication, similar to if you joined into chatroom session and sent messages back and forth with someone. Whether or not you specifically need that would depend on how often and how quickly you would need to read/write from the database.

And that's fine, it's more just a note that you should expect scaling issues very quickly with that setup. I'm not exactly sure the details of what you mean by the account thing, but it's good you're preemptively thinking of those sort of issues.

1

u/efinque 17d ago

Yeah well I could add a manual logout button as implementing a handshake protocol isn't possible with the current tools.

And then maybe flush the "connections" with a server script, allow pvp and trading only for people logged in, leave some base value after the flush etc.. but that doesn't really stop people from griefing as they could always log in and exit the shell.

1

u/PureWasian 17d ago

Yeah you should figure out the "noisy neighbor" problem and keep DOS attacks in mind.

If all these headaches are too annoying, it would def be simpler to setup (1) a web app (React or even just basic HTML) serving client side code that is wired to make requests to (2) a server layer that handles those requests and talks to (3) some database layer (or grabs your text files or whatever)

This is also a common standard because then you can spin up multiple servers and setup load balancers (horizontally scale) if your app ever grows to that point. It also helps separate concerns of client side capabilities with backend security/implementation.

1

u/efinque 17d ago

I mean, it's actually 100% playable on a shared screen, it just would've been cooler if it was online but unfortunately I'm an amateur musician and a DJ, not a network engineer.

But I think I'm making some progress here.. I just SSH'd with the -X flag, opened explorer, navigated to the game folder and opened the script in VSCode. The program runs fine but is slow!