Docker for api about solana-playground

[katopz]

The title maybe mislead 🤔. It would be "Do api have Run endpoint for rust client? If not (it's not i guess), maybe you can provide current api Docker file so I can I help add that Run endpoint.

I expected something like rust playground + solana related create.
After that in ui should have separated section for both program and client side and run button something like...

and when click run it should call https://api.solpg.io/run and get the result back at cli.

Motivation

When user open the repos that contain both program and (simple) rust client. They should able to run both in playground.

Anyway JIT ts and lazy load module should be more suitable (widely used) than rs client example.
But I'm kinda bore to mess with ts so I propose to take care of rust client example instead. 😅

And again, nothing serious here, just itchy to having fun with the playground.

[katopz]

1. i can see nearly most example and test use new KeyPair() in ts or embed byte keypair in rs which mean it should be fine for example purpose on devnet and maybe some serious warning (or blocking) for mainnet

2. 3. 4. Can be address with money or subscription (no joy), anyway I'm agree we should get back to this when things viable.

I will try POC ts way while wait. 👍

[acheroncrypto]

Can you expand on this? Would love to hear how exactly this would work.

[acheroncrypto]

Would love to have something like this but I think there are a few problems with this approach.

1. The server would need the keypair of the user to make this work
2. The server would need internet access
3. The server would need premium RPC endpoints on all networks to serve all those requests. Any free RPC provider would block the IP since we are sending it from the same location
4. This would also add lots of load to the server(trying to do as little as possible from the server, that's why we are using wasm for the CLI's even though it would have been much easier to just have a server for it)

TS/JS sounds good for this purpose to do everything in the client. For now though, the main goal is to do the tests from the UI to have a different value proposition.

This would be great to return back to when browser tooling for Rust improves and we can do most if not all of these from the client.