memoize VS webssh

I totally agree, though I think those articles are a lot harder (eg requiring more skill) to write well because you need to quickly ramp your readers on all of whatever the context is that's necessary to actually appreciate the nuance of the design decisions under discussion. You're basically by definitely going to be out of the realm of "just follow best practice X" or "apply pattern Y or you're doing it wrong."

As a small example, I've been working on a small asyncio-based web service (Python) which is oriented around an expensive process that generates a result, where the result is stashed in sqlite and returned. I knew upfront that I needed a way to track when a particular result was already being prepared so that if I got a second request for it, it would collapse it into the first one and only do the work once. I wrote this as a twenty line memoizing decorator, but it turns out this issue as a name— cache stampeding. Once I realized that, I discovered that there are existing (and much more complicated/tunable) solutions to this problem, such as https://github.com/DreamLab/memoize/, but the article pitching that solution spends quite a bit of time getting to it— enough so that if I'd discovered it before building my own, I'm not sure I would even have appreciated its applicability:

https://tech.ringieraxelspringer.com/blog/open-source/cachin...

I'm trying to be able to automatically connect to SSH in the browser via just a URL. I've got https://github.com/huashengdun/webssh running, and I can pass a lot of it via query parameters, except the private key.

I am creating a web application where i want to open ssh terminal (https://github.com/huashengdun/webssh) with an event listener on frontend and spawn() method in backend nodejs. I built an api to trigger that command from front-end but the problem is that the it's returning stderr which is fine but how can i handle that in my frontend as i want to show the terminal in but my api is not giving any response. Is there any other way to make this script.

This is my nodejs file where i am passing data from axios and executing the wssh command to start the webssh.

const child = spawn('wssh', [\${body.cert_option}`, `${body.key_option}`, `--log-file-prefix=/var/www/html/myPanel/logs/terminal.log`]); child.stdout.on('data', (data) => { console.log(`stdout: ${data}`); return res.status(500).json({ success: 0, data: data }); }) child.stderr.on('data', (data) => { console.log(`stderr: ${data}`); return res.status(200).json({ success: 1, data: data }); }); child.on('error', (error) => { console.log(`error: ${error}`); return res.status(500).json({ success: 0, message: "SSH connection error", error: error }); }); child.on('exit', (code, signal) => { if (code) { console.log(`child process exited with code ${code}`); } if (signal) { console.log(`child process exited with signal ${signal}`); } }); });`

PS: my project is not completely on nodejs, only the api.

So here is something i want to create like this (source: aapanel):

https://preview.redd.it/203hx6mzpy791.png?width=1349&format=png&auto=webp&s=d5cbbf22fe0d4cf4e6b7566d45f8d1957798ba8a

As mentioned by others, this isn't a good but is doable. Here is how: * install https://github.com/huashengdun/webssh on the web servers / applications behind your ALB * add OIDC authentication to the ALB tier for the URL you are exposing the web SSH client under (optional but recommended). This limits access to the web client

Perhaps WebSSH?