04:01 <seydar> given that a manage all of my gems as my local user... what's the preferred way to run a sinatra program on port 80 with sudo?

13:50 <Doc_X> For a comparison of language popularity, you can check out https://spectrum.ieee.org/top-programming-languages-2022 or https://www.stackscale.com/blog/most-popular-programming-languages/ to see relative comparisons... Python being adopted early by Google as their de facto scripting language really helped it supplant Ruby as the heir apparent to Perl a decade or so ago.

13:51 <Doc_X> that said, there are a good number of shops that run ruby (for more than just Ruby on Rails). I do a lot of my personal scripting in it when I'm not forced elsewhere by library availability.

13:52 <Doc_X> seydar: You should be able to do `set :port, 80` in the sinatra config (per https://sinatrarb.com/configuration.html). . . but as you say you'll need to run via sudo.

15:10 <wnd> I'd consider using nginx, socat, or such to listen to port 80

15:19 <ox1eef_> He is not in the channel. But yeah, I'd use nginx, or puma-dev.

17:30 <Doc_X> one of the downsides of ignoring join/part messages. apologies for the noise.

19:22 <havenwood> Or live a little on the bleeding edge with Falcon.

19:22 <havenwood> It works well without an NGINX reverse proxy.

21:23 <svdasein> I'm having not such a good time trying to get an interactive shell going (with a network device) using Net::SSH. Looks like there used to be a built in method called shell that is obsolete. And then someone wrote a gem net-ssh-shell that I guess was supposed to replace that but that hasn't been maintained for a long time. And I'm finding a dearth (almost none) of information as to how to do it with the current Net::SSH. Anyone have

21:23 <svdasein> experience w/ that sort of thing? The problem is I need a stateful shell similar to like "cd /my/dir\nls\n" - the exec! method won't work for my use case cuz there's a required state change before the command I actually wanna run.

21:42 <svdasein> I am beginning to think it might be some fundamental problem with cisco's ssh stack on this device - but unsure...

21:44 <ox1eef_> So long as you think with evidence, that's fair.

21:45 <svdasein> the technique I'm using on the cisco device does not behave the same way when talking to sshd on a linux device

21:54 <svdasein> nm figured it out